Overview
The flow has nine steps, executed in order:Prerequisites
- A registered application with Stellar credentials and a connect secret
- An authenticated Business session (OTP or OAuth)
- A beneficiary with at least one payment destination
Step by step
List associations
Retrieve the associations (organisations) your application has access to:Pick the
associationId you want to operate with.List wallets
Get the wallets available for that association:Select the wallet that holds the asset you want to send from.
Get the beneficiary
Look up the beneficiary who will receive the payment:The response includes the beneficiary’s payment destinations (bank accounts, mobile money wallets, etc.).
Authenticate for Connect
The Connect lane requires Ed25519 authentication with your application’s Stellar keypair:
Discover available connectors
Find which payment connectors can deliver to your beneficiary’s destination:The response lists connectors with their supported corridors, methods, and accepted assets.
Get a Connect quote
Request a quote from the selected connector:The quote includes the exchange rate, fees, the destination amount, and a
quoteId for execution.Get a Stellar quote (if needed)
If your wallet holds a different asset than what the connector accepts, get an on-chain path-payment quote:This returns the
sendMax value needed for the Stellar transaction.Execute the Stellar transaction
Fund the payment by sending the asset to the connector’s clearing account:On success, you receive a Stellar transaction hash.
Using the Go SDK
The SDK provides aConnectPayment recipe that orchestrates all nine steps:
Tracking payment status
After execution, query the payment status:Auth requirements
| Step | Auth required | |
|---|---|---|
| Steps 1-3 (Business data) | Business session (OTP or OAuth) | |
| Step 4 (Ed25519 login) | Stellar keypair | |
| Steps 5-9 (Connect) | Connect bearer + x-zeam-auth connect secret |

