Instant Payments OBO Enhancements Guide
Submit an Instant Payment OBO using counterparty details on the external Synthetic Account, ultimate debtor details in the transmitter section, and initiator_type set to transmitter.
Submit an Instant Payment on behalf of another party by storing the counterparty details on the external Synthetic Account and supplying the ultimate debtor details in the Transfer's transmitter section.
Before you begin
- Configure API access using the Authentication Guide.
- Identify the source Synthetic Account and confirm sufficient available funds.
- Review the Instant Payments guide for payment requirements and receiving-bank eligibility.
Submit an OBO payment
- Configure the counterparty. Provide the counterparty (the payment recipient) data in the Instant Payment object on the external Synthetic Account. Use Create a New Synthetic Account for the account fields and validation requirements.
- Provide the ultimate debtor. When initiating the Transfer, supply the ultimate debtor (the party on whose behalf you are sending the payment) details in the transmitter section. Use Initiate a Transfer for the required transmitter fields.
- Select the transmitter initiator type and submit the Transfer. Set
initiator_typetotransmitterand include the required source account, destination account, amount, and Instant Payment fields documented in the Transfer reference.
Important: initiator_type defaults to customer. If you omit it or leave it set to customer, supplied transmitter information is ignored. Set it explicitly to transmitter when submitting an OBO payment.
A successful initiation returns HTTP 201; it does not confirm settlement.
Follow the standard Instant Payments flow
OBO does not change authorization considerations, transfer lifecycle behavior, or event monitoring. Follow the Instant Payments guide, Transfer Statuses, and Notifications for those parts of your integration.
Related documentation
Updated 8 days ago

