Cookbooks and recipes home
This page contains recipes that are designed to help you use and integrate Payabli. Recipes are short tutorials that cover a workflow. We’ve organized these by Payabli product area.
This page is under construction, we’re working hard to bring you more recipes and cookbooks. Stay tuned!
General recipes
Recipe: Authentication guide
/// Step 1: Get your API tokenNavigate to PartnerHub > Developers > API Tokens and create a new organization token. Your API tokens carry privileges, so keep them secure!
Your token will look something like this:
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
/// Step 2: Add token to request headers
Send the API token in the request header with the key requestToken. All API requests must be made over HTTPS.
/// Step 3: Add idempotency key (recommended)
Include a unique idempotencyKey header to prevent duplicate transactions. This key persists for 2 minutes.
Learn more about authentication, API tokens, and idempotency in API overview.
Pay In recipes
Use these recipes to get you started with Pay In features and functions. See Pay In overview for more.
Recipe: Run your first sale transaction
/// OverviewThis end-to-end workflow walks through how to run a card sale transaction using the API. The getpaid endpoint authorizes and captures the transaction in one step, so it’s immediately captured for settlement. This recipe uses the v2 transaction API, which all new integrations should use.
/// Prerequisites
Before you start, make sure you have the following:
- Your paypoint’s
entryPointvalue - A
customerIdfor the customer making the payment. If you don’t have one, create a customer first. - The customer’s payment details: for a card transaction, this includes the card number, expiration date, CVV, and billing ZIP code
PCI compliance note: This recipe passes raw card data directly through the API for demonstration purposes. In production, use an embedded component to collect card details, or use a stored payment method, which keeps your PCI scope minimal. If you handle raw card data directly, your PCI scope is expanded and you must secure cardholder data and customer IP addresses.
/// Step 1: Run the sale transaction
Send a POST request to /api/v2/MoneyIn/getpaid with the payment method, amount, and customer information. This authorizes and captures the transaction in one step.
A successful response returns code A0000 (Approved) and a paymentTransId in the data object that you can use to look up the transaction later.
See Make a transaction (v2) for the full API reference.
/// Step 2: Check the transaction status
Use the paymentTransId from the previous step to check the transaction’s status and details.
Send a GET request to /api/MoneyIn/details/{paymentTransId}.
Since the getpaid endpoint authorizes and captures in one step, the transStatus is Captured (1). To track settlement progress, watch the settlementStatus field as it moves from Pending (0) through In Transit (1), Transferred (2), and Funded (3). See the Pay In lifecycle for more.
See Get details for a processed transaction for the full API reference.
/// What’s next
Congratulations! You just ran your first sale transaction. Next, learn about the Pay In transaction lifecycle and explore running transactions with other payment methods.
Recipe: Create a customer
/// OverviewCreate a customer record in Payabli to track payers, store payment methods, and manage subscriptions. Customer records require at least one identifier field.
/// Prerequisites
Before you start, make sure you have the following:
- Your paypoint’s
entrypointvalue - At least one customer identifier:
firstnameandlastname,email, or a custom identifier
Check your identifier settings in Settings > Custom Fields in PartnerHub. See custom identifiers for more.
/// Create the customer
Send a POST request to /api/Customer/single/{entry} with the customer’s details. Include identifier fields so Payabli can match against existing records.
The response includes a customerId that you can use with other endpoints to manage the customer and run transactions.
See Add customer for the full API reference.
/// What’s next
Congratulations! You’ve created a customer record. Learn more about managing customers with the API and customer entities in Payabli.
Recipe: Refund a transaction
/// OverviewRefund a settled Pay In transaction to return funds to the customer. You can refund the full amount or a partial amount. This recipe uses the v2 API.
/// Prerequisites
Before you start, make sure you have the following:
- The
referenceIdof a settled transaction (also called thetransId) - The refund amount, if you’re issuing a partial refund
If the transaction hasn’t settled yet, void it instead.
/// Refund the transaction
For a full refund, send a POST request to /api/v2/MoneyIn/refund/{transId}. For a partial refund, append the amount: /api/v2/MoneyIn/refund/{transId}/{amount}. The refund amount excludes any service fee charged on the original transaction.
This example refunds the full transaction amount:
A successful refund returns a code of A0004 with a reason of “Refunded”. The data object contains the full transaction details.
To refund a partial amount, include the amount in the path. This example refunds $100.99:
See Refund a settled transaction (v2) for the full API reference.
/// What’s next
Congratulations! You’ve refunded a Pay In transaction. Learn about choosing between void and refund and the Enhanced Refund Flow.
Recipe: Void a transaction
/// OverviewVoid an unsettled Pay In transaction to cancel it before the batch closes. Voids cancel the full transaction amount — partial voids aren’t supported. This recipe uses the v2 API.
/// Prerequisites
Before you start, make sure you have the following:
- The
referenceIdof an unsettled transaction (also called thetransId)
If the transaction has already settled, refund it instead.
/// Void the transaction
Send a POST request to /api/v2/MoneyIn/void/{transId}.
A successful void returns a code of A0003 with a reason of “Canceled”. The data object contains the full transaction details.
If you try to void a transaction that has already been settled or voided, the API returns a 400 status.
See Void a transaction (v2) for the full API reference.
/// What’s next
Congratulations! You’ve voided a Pay In transaction. Learn about choosing between void and refund and explore other cancellation methods.
Recipe: Charge a saved payment method
/// OverviewCharge a returning customer using a payment method you’ve already tokenized and stored, without collecting their card or bank account details again. This recipe uses the v2 transaction API, which all new integrations should use.
/// Prerequisites
Before you start, make sure you have the following:
- A
storedMethodIdfor the customer’s saved payment method. If you haven’t saved one yet, see Save a payment method. - The
customerIdfor the customer who owns the stored method - Your paypoint’s
entryPointvalue - Know whether the stored method is a
cardorachmethod, so you can set themethodfield correctly
/// Step 1: Run the transaction
Send a POST request to /api/v2/MoneyIn/getpaid with the storedMethodId in the paymentMethod object instead of raw card or bank account details.
Set initiator to payor for customer-initiated transactions, or merchant for merchant-initiated transactions. See CIT and MIT overview for guidance on which to use.
A successful response returns code A0000 (Approved) and a paymentTransId in the data object that you can use to look up the transaction later.
See Make a transaction (v2) for the full API reference.
/// Step 2: Check the transaction status
Use the paymentTransId from the previous step to check the transaction’s status and details.
Send a GET request to /api/MoneyIn/details/{paymentTransId}.
Since the getpaid endpoint authorizes and captures in one step, the transStatus is Captured (1). To track settlement progress, watch the settlementStatus field as it moves from Pending (0) through In Transit (1), Transferred (2), and Funded (3). See Pay In lifecycle for more.
See Get details for a processed transaction for the full API reference.
/// What’s next
Congratulations! You just charged a saved payment method. Next, learn about tokenization and explore other ways to make transactions.
Recipe: Send a payment link
/// OverviewGenerate a payment link from an existing invoice and send it to a customer via email. Payment links direct customers to a hosted payment page where they can pay using your accepted methods.
/// Prerequisites
Before you start, make sure you have the following:
- An
idInvoicefor an invoice created via the API. If you haven’t created one yet, see Manage invoices. - Your paypoint’s
entryPointvalue - The customer’s email address
/// Step 1: Generate the payment link
Create a payment link from your invoice. You can customize the hosted payment page’s branding, accepted payment methods, and layout.
Send a POST request to /api/PaymentLink/{idInvoice}.
The response includes the payment link ID in responseData. You need this ID to send the link in the next step.
See Create payment link from invoice for the full API reference.
/// Step 2: Send the payment link
Send the payment link to the customer via email. You can include additional recipients and attach a PDF invoice.
Send a POST request to /api/PaymentLink/push/{payLinkId}.
A successful response returns the payLinkId and a success message.
See Send payment link for the full API reference.
/// What’s next
Congratulations! You just sent a payment link to your customer. Next, learn about choosing an invoice delivery strategy and explore all the ways to manage payment links.
Recipe: Create and send an invoice
/// OverviewCreate a one-time invoice for a customer and send it via email with an attached PDF. This recipe covers the two-call workflow: create the invoice, then send it.
/// Prerequisites
Before you start, make sure you have the following:
- Your paypoint’s
entryPointvalue - A
customerIdfor an existing customer. If you haven’t created one yet, see Manage customers. - Invoice details: line items, amounts, and a unique invoice number
/// Step 1: Create the invoice
Create the invoice linked to an existing customer. The request includes customer identification, line items, amount, and invoice metadata.
Send a POST request to /api/Invoice/{entry}.
The response includes the invoice ID in responseData. You need this to send the invoice in the next step.
See Add invoice for the full API reference.
/// Step 2: Send the invoice
Email the invoice to the customer. Use attachfile=true to include a PDF copy, and mail2 to specify the recipient email address. If you omit mail2, Payabli sends the invoice to the email address on file for the customer.
Send a GET request to /api/Invoice/send/{idInvoice}.
See Send invoice via email for the full API reference.
/// What’s next
Congratulations! You just created and sent an invoice. Next, explore the full invoice lifecycle in Manage invoices with the API and learn how to choose an invoice delivery strategy.
Recipe: Retrieve batches and transfers
/// OverviewRetrieve a list of batches and transfers for a paypoint to monitor settlement activity. A batch is a group of transactions that are settled together at the end of a processing cycle. A transfer is the actual movement of funds from the batch into the paypoint’s bank account.
/// Prerequisites
Before you start, make sure you have the following:
- Your paypoint’s
entrypointidentifier - An API token with access to the paypoint. See the authentication recipe for help
/// Step 1: Get batches for the paypoint
Query the batches endpoint to retrieve settlement batches for a paypoint. Each batch groups transactions and, once transferred, includes a Transfer object with deposit details.
Send a GET request to /api/Query/batches/{entry}.
The response includes batch records. If a batch has been transferred, the Transfer object contains the transfer details. If Transfer is null, the batch hasn’t been transferred yet.
See List batches for paypoint for the full API reference.
/// Step 2: Get transfers for the paypoint
Query the transfers endpoint to get deposit records with adjustment details like chargebacks, ACH returns, and fees.
Send a GET request to /api/Query/transfers/{entry}.
The response includes transfer records with gross amounts, deductions, and the net amount deposited.
See List transfers for the full API reference.
/// What’s next
You’ve retrieved batches and transfers for a paypoint. To track chargebacks and ACH returns within transfers, see Reconcile adjustments in transfers. For more on how batches and transfers relate, see How money moves.
Recipe: Set up autopay on an invoice
/// OverviewSet up recurring automatic payments on an invoice by creating a subscription that references it. In this example, a customer owes 150 per month over 12 months. Each subscription payment automatically posts against the invoice.
/// Prerequisites
Before you start, make sure you have the following:
- Your paypoint’s
entryPointvalue - A
customerIdfor an existing customer. If you haven’t created one yet, see Manage customers. - Invoice details: line items, amounts, and a unique invoice number
- A
storedMethodIdfor the customer’s saved payment method. To save a method, see Save a payment method. - A schedule for the autopay: start date, end date (or open-ended), and frequency
/// Step 1: Create the invoice
Create a one-time invoice for the customer. This is the invoice that subscription payments will post against.
Send a POST request to /api/Invoice/{entry}.
In the next step, you use the same invoiceNumber to link the subscription to this invoice.
See Add invoice for the full API reference.
/// Step 2: Create a subscription with the invoice
Create a subscription that charges 1,800 invoice from step 1. The invoiceNumber in the subscription request must match the one you set when creating the invoice — this is what ties the payments to the invoice. The scheduleDetails.frequency controls when payments run, while invoiceData.frequency describes the invoice itself — keep the invoice as "onetime" and let the subscription handle the recurrence.
Send a POST request to /api/Subscription/add.
The response includes the subscription ID in responseData and the linked customerId.
See Create subscription for the full API reference.
/// What’s next
Congratulations! You just set up autopay on an invoice. Next, learn how to manage and update subscriptions and explore the full invoice lifecycle in Manage invoices with the API.
Pay Out recipes
Use these recipes help get you started with Pay Out features and functions. See Pay Out overview for more.
Recipe: Make your first payout
/// OverviewThis complete end-to-end workflow walks through how to send a payment to a vendor using ACH.
/// Step 1: Create a vendor
First, make sure that you have a vendor record. If you already have a vendorNumber, you can skip to step 2.
To create a vendor, send a POST request to /api/Vendor/single/{entry}.
You need the vendorNumber you set for the vendor in the next step.
See Create vendor for the full API reference.
/// Step 2: Create a bill for the vendor
Send a POST request to /api/Bill/single/{entry} to add a bill that represents the invoice you need to pay. This is optional but strongly recommended for tracking.
The billId is returned in responseData. Copy this to use in the next step.
See Create bill for the full API reference.
/// Step 3: Authorize the payout transaction
Authorizing a payout creates the transaction, which is captured for processing later.
To authorize a payout, send a POST request to /api/MoneyOut/authorize.
The response includes a referenceId (for example, "129-001") that you need to capture the payout for processing in the next step.
See Authorize a transaction for payout for the full API reference.
/// Step 4: Capture the payout for settlement
Capturing an authorized payout adds it to a batch for processing.
To capture the payout, send a GET request to /api/MoneyOut/capture/{referenceId}.
The payout is now captured and will process with the next batch at 5 PM ET.
See Capture an authorized payout transaction for the full API reference.
/// Step 5: Monitor transaction status
Check the transaction status as it progresses through the payment lifecycle.
To get the transaction details, send a GET request to /api/MoneyOut/details/{referenceId}.
Watch for the status to progress: 1 (Captured) → 2 (Processing) → 3 (Processed) → 5 (Paid).
- Learn more about Pay Out statuses.
- See Get details for a processed payout transaction for the full API reference.
/// What’s next
Congratulations! You just processed your first payout. Next, get to know payables and learn more about managing payouts.
Recipe: Create a vendor
/// OverviewAdd a new vendor record with bank account details for ACH payments.
/// Prerequisites
Before you start, gather the following information. Payabli supports US and Canadian vendors only.
- Vendor business information: name, email, phone, and address
- A
vendorNumberto identify the vendor in your system - Bank account details for ACH payments: routing number, account number, account type, and account holder name
Including bank account details in billingData is not supported if you use managed payouts.
/// Step 1: Create the vendor
Send a POST request to /api/Vendor/single/{entry} to create the vendor. The entry parameter is your entrypoint identifier.
The response returns the Payabli-generated vendorId in responseData.
See Create vendor for the full API reference.
Recipe: Create ACH payout
/// OverviewSend a payment to a vendor via ACH bank transfer with full transaction lifecycle. This recipe is for on-demand payouts and is not supported with managed payouts.
/// Prerequisites
Before you start, make sure you have the following:
- A
vendorNumberfor the vendor you’re paying - The vendor’s ACH information: account holder name, routing number, account number, and account type (checking or savings)
- A
billIdif you’re paying against a bill (recommended)
/// Step 1: Authorize the payout
Authorize the payout. This queues the transaction but doesn’t process it until captured.
To authorize a payout, send a POST request to /api/MoneyOut/authorize.
The response includes a referenceId that you need to capture or cancel the transaction.
See Authorize a transaction for payout for the full API reference.
/// Step 2: Capture the payout
Capture the authorized transaction to add it to a batch for processing. Batches close at 5 PM ET.
To capture the payout, send a GET request to /api/MoneyOut/capture/{referenceId}.
See Capture an authorized payout transaction for the full API reference.
/// Step 3: Monitor transaction status
Check the transaction details to monitor the payout through its lifecycle: Captured → Processing → Processed → Paid.
To get the transaction details, send a GET request to /api/MoneyOut/details/{referenceId}.
See Get details for a processed payout transaction for the full API reference.
/// Step 4: (Optional) Cancel if needed
You can cancel authorized or captured transactions before the batch closes at 5 PM ET.
To cancel a payout, send a DELETE request to /api/MoneyOut/cancel/{referenceId}.
See Cancel a payout transaction for the full API reference.
Recipe: Create vCard payout
/// OverviewThis recipe walks through issuing a single-use virtual card to a vendor and sending the card link via email. This recipe is for on-demand payouts and is not supported with managed payouts.
/// Prerequisites
Before you start, make sure you have the following:
- A
vendorNumberfor the vendor you’re paying - The vendor’s email address to send the card link to
/// Step 1: Create the virtual card payout
Authorize a payout with method: "vcard". This creates a single-use virtual card for the vendor.
To authorize the payout, send a POST request to /api/MoneyOut/authorize.
The response includes a referenceId that you need to capture the payout transaction.
See Authorize a transaction for payout for the full API reference.
/// Step 2: Capture the transaction
Capture the authorized vCard payout to issue the card.
To capture the payout, send a GET request to /api/MoneyOut/capture/{referenceId}.
See Capture an authorized payout transaction for the full API reference.
/// Step 3: Send the card link
Send the vendor an email with a secure link to view their virtual card details.
To send the card link, send a POST request to /api/vcard/send-card-link.
See Send vCard link for the full API reference.
/// Step 4: Monitor for payment
When the vendor uses the vCard, the transaction status changes to Paid. vCards remain open for 180 days if not used.
Learn more about Pay Out statuses.
Recipe: Create check payout
/// OverviewSend a physical check payment to a vendor with the authorize-and-capture workflow. This recipe is for on-demand payouts and isn’t supported with managed payouts.
/// Prerequisites
Before you start, make sure you have the following:
- A
vendorNumberfor the vendor you’re paying - The vendor record must have
payeeName1set — this is the name printed on the check - A
billIdif you’re paying against a bill (strongly recommended)
/// Step 1: Authorize the payout
Authorize a payout with method: "check". This queues the transaction but doesn’t process it until it’s captured.
To authorize a payout, send a POST request to /api/MoneyOut/authorize.
The checkNumber field is optional. If you don’t include one, Payabli automatically manages check numbering and sequencing.
The response includes a referenceId that you need to capture or cancel the transaction.
See Authorize a transaction for payout for the full API reference.
/// Step 2: Capture the payout
Capture the authorized transaction to add it to a batch for processing. Batches close at 5 PM ET. After capture, Payabli generates and mails the physical check.
To capture the payout, send a GET request to /api/MoneyOut/capture/{referenceId}.
See Capture an authorized payout transaction for the full API reference.
/// Step 3: Monitor transaction status
Check the transaction details to monitor the payout through its lifecycle: Captured → Processing → Processed → Paid.
To get the transaction details, send a GET request to /api/MoneyOut/details/{referenceId}.
See Get details for a processed payout transaction for the full API reference.
/// Step 4: (Optional) Cancel if needed
You can cancel authorized or captured transactions before the batch closes at 5 PM ET. Once the status changes to Processed, you can’t cancel the transaction.
To cancel a payout, send a DELETE request to /api/MoneyOut/cancel/{referenceId}.
See Cancel a payout transaction for the full API reference.
/// What’s next
You’ve created a physical check payout. Learn about retrieving check images for record-keeping, or set up Positive Pay for fraud prevention.
Recipe: Approve and pay a bill
/// OverviewRoute a bill through approval and make a payout. This recipe covers the approval workflow from submission to payout.
/// Prerequisites
Before you start, make sure you have the following:
- An existing bill with its
idBill— see Create bill or the manage bills guide - The vendor’s payment information (ACH details or stored method)
- Approver email addresses for your approval workflow
/// Step 1: Send the bill for approval
Submit the bill to one or more approvers by passing an array of their email addresses. The bill status changes to “Sent to Approval”.
Send a POST request to /api/Bill/approval/{idBill}.
See Send bill for approval for the full API reference.
/// Step 2: Approve or reject the bill
Approvers can approve or reject the bill through the Payabli Portal or through the API. To approve or reject programmatically, use true to approve or false to reject.
Send a GET request to /api/Bill/approval/{idBill}/{approved}.
See Approve bill for the full API reference.
/// Step 3: Verify the bill status
Confirm the bill is approved and ready for payout.
Send a GET request to /api/Bill/{idBill}.
Check the Status field in the response. A status of 1 (Active) or 20 (Approved) means the bill is ready for payout.
See Get bill for the full API reference.
/// Step 4: Authorize the payout
Create a payout authorization that references the approved bill.
Send a POST request to /api/MoneyOut/authorize.
The response includes a referenceId that you need to capture the payout.
See Authorize payout for the full API reference.
/// Step 5: Capture the payout
Capture the authorized transaction to process the payment.
Send a GET request to /api/MoneyOut/capture/{referenceId}.
See Capture payout for the full API reference.
/// What’s next
You’ve approved and paid a bill. Learn more about managing bills with the API and explore the ACH payout recipe for more payout options.
Recipe: Send a vendor payment link
/// OverviewGenerate a payment link for a bill and send it to a vendor via email. The vendor selects their preferred payout method (ACH, virtual card, or check) on a secure, hosted page. When they complete it, Payabli automatically authorizes and captures the payout.
/// Prerequisites
Before you start, make sure you have the following:
- A vendor associated with the bill. If you haven’t created one yet, see Manage vendors.
- A
billIdfor an existing bill. If you haven’t created one yet, see Manage bills. - The vendor’s email address
- Your paypoint’s available payout methods (ACH, virtual card, check)
/// Step 1: Generate the payment link
Create a payment link tied to the bill. Don’t include the mail2 query parameter — you’ll send the link in the next step instead.
Send a POST request to /api/PaymentLink/bill/{billId}.
The response includes the payment link ID. Save this — you’ll need it to send the link in the next step.
See Generate payment link from bill for the full API reference.
/// Step 2: Send the payment link
Send the link to the vendor’s email. To send to additional recipients beyond the vendor’s email on file, add their addresses to the mail2 query parameter, separated by semicolons.
Send a GET request to /api/PaymentLink/send/{payLinkId}.
See Send payment link for the full API reference.
/// What’s next
Congratulations! You just sent a vendor payment link. The vendor’s payment method preference is stored automatically for future payouts. Learn more about managing vendor payment links and managing payouts.
Recipe: Reissue a payout
/// OverviewReissue a payout transaction with a different payment method when the original can’t be completed. This recipe covers reissuing as ACH, check, or virtual card. Reissuing is for on-demand payouts only — it isn’t supported with managed payouts.
/// Prerequisites
Before you start, make sure you have the following:
- The
transIdof the original payout transaction - The original transaction must be in Processing or Processed status
- The new payment method details (ACH bank account details, or just the method type for check or virtual card)
- If the original was a check, contact Payabli support to stop the original check before reissuing
/// Step 1: Reissue the payout
Send a POST request to /api/MoneyOut/reissue with the original transaction ID as a query parameter and the new payment method in the request body.
The example below reissues a payout as ACH. For check, set method to "check" (no additional fields needed — the check is mailed to the remittance address from the original transaction). For virtual card, set method to "vcard".
A successful response returns the new transaction ID and a link to the original transaction.
The new transaction goes through the standard authorize-and-capture flow automatically. Check the isSuccess field in the response — an HTTP 200 doesn’t always mean the reissue succeeded.
See Reissue payout for the full API reference.
/// Step 2: Verify the reissue
Check the new transaction’s details to confirm it was created and monitor its progress through the lifecycle.
Send a GET request to /api/MoneyOut/details/{transId}, using the transactionId from the reissue response.
The response includes an Events array that links back to the original transaction for audit purposes.
See Get details for a processed payout transaction for the full API reference.
/// What’s next
You’ve reissued a payout with a new payment method. Learn more about reissue rules and error handling and the payout transaction lifecycle.
Recipe: Create a managed payout
/// OverviewCreate a payout where Payabli’s vendor enablement team contacts the vendor and determines the best payment method. For more details on the enablement process, see Managed payables overview.
/// Prerequisites
Before you start, make sure you have the following:
- A
vendorNumberfor the vendor you’re paying - The vendor’s contact name, phone number, and email address on their vendor record — the vendor enablement team needs these to reach the vendor
- A remittance address for the vendor, in case the payment falls back to a physical check
/// Step 1: Create a bill
Add a bill that represents the invoice you need to pay. This step is optional but strongly recommended for tracking. If you already have a billId, skip to step 2.
To create a bill, send a POST request to /api/Bill/single/{entry}.
The billId is returned in responseData. Copy this to use in the next step.
See Create bill for the full API reference.
/// Step 2: Authorize the payout
Authorize the payout with method: "managed". This tells Payabli to handle vendor enablement and payment method selection automatically.
To authorize a payout, send a POST request to /api/MoneyOut/authorize.
The response includes a referenceId that you need to capture the transaction.
See Authorize payout for the full API reference.
/// Step 3: Capture the payout
Capture the authorized transaction. After capture, Payabli’s vendor enablement team contacts the vendor within 36 business hours to determine the best payment method — starting with vCard, then ACH, then physical check.
To capture the payout, send a GET request to /api/MoneyOut/capture/{referenceId}.
See Capture payout for the full API reference.
/// Step 4: Monitor transaction status
Check the transaction status as it progresses through the managed payables lifecycle.
To get the transaction details, send a GET request to /api/MoneyOut/details/{referenceId}.
Watch for the status to progress: 1 (Captured) → 2 (Processing) → 3 (Processed) → 5 (Paid).
- Learn more about Pay Out statuses.
- See Get payout details for the full API reference.
/// What’s next
You just created a managed payout. Next, learn more about the vendor enablement process and how to manage payouts.
Pay Ops recipes
Coming soon!