Send Steps & API Overview

A user journey guide for making a send to your customers, including the API reference at the right time.

API reference	What's returned from the API	User journey step	What to show on the UX	What to ask the user for
Retrieve Get Channels	A list of available payment channels for the given country including limits	User chooses a preferred payment channel	List of payment channels available to them eg: Bank Transfer, mobile money, P2P transfer	Their preference of payment method
Get Rates	Limits for a given payment channel Rate of USD/ Fiat currency conversion	User confirms amount to be paid out to them	Confirmation of amount user to receive	Confirmation
Get Networks Reason for sending = Payment Reasons	A list of available networks (i.e Bank or Mobile Money) Payment Reasons - Pre-defined list of reasons to select.	Enter receiving details & reason for sending	Bank transfer/ P2P Bank name (Select the bank of the beneficiary) Account holder name Account number Mobile Money First name Last name Mobile number (code +string) Mobile provider	Please provide account details and select the reason for sending:
Submit Send Request	A quote to make the send	Confirm send amount & details	Show Transaction details including: Payment Channel Payment Network Recipient details entered Total amount Rate Ability to confirm or cancel.	To confirm or cancel the requested transaction.
Accept Send Request Deny Send Request	Confirmation or cancellation of the transaction	End of flow confirmation	Confirmation the send is being processed / cancelled	n/a
n/a Webhooks to determine status of transaction	n/a	Customer receives local fiat in bank account or mobile wallet.	n/a	n/a
Lookup Send	Information about a specific send	Retrieve information about a specific send	View transaction details	View transaction details

To get started, open the recipe below:

Making a send in Latin America

Outbound sends to Latin America follow the same steps above and support MXN (Mexico via SPEI), BRL (Brazil via PIX), COP (Colombia), and ARS (Argentina). For COP and ARS, standard local bank account details apply.

Making a USD/EUR send

Making a USD/EUR send in select Asian, European, African, and South American countries follows the steps outlined in the recipe below. The request body contains fields that are specific to USD/EUR payments.

Required Fields

All Countries

The following fields are required on every USD/EUR send, regardless of country.

Top-level request:

Field	Type	Description
customerType	string	Must be "institution"
purposeOfRemittance	string	See Payment Reasons

Sender object:

Field	Type	Description
businessName	string	Legal name of the sending business
businessId	string	Business registration or tax ID

Destination object:

Field	Type	Description
accountName	string	Name of the account holder
accountNumber	string	Bank account number
accountType	string	Must be "bank"
networkId	string	YC network ID for the receiving bank
businessName	string	Legal name of the receiving business
documentReferenceNumber	string	Reference document number (e.g. invoice number)

Country-Specific Fields

France (FR) — EUR

Field	Location	Description
accountNumber	destination	Must be a valid IBAN (e.g. FR7630006000011234567890189)

Cambodia (KH) — USD

Field	Location	Description
businessAddress	destination	Full business address of the recipient

Sri Lanka (LK)— USD

Field	Location	Description
phoneNumber	destination	Recipient phone number in international format
businessId	destination	Business registration ID of the recipient

Ecuador (EC)— USD

Field	Location	Description
phoneNumber	destination	Recipient phone number in international format
taxId	destination	Recipient tax identification number
bankAccountType	destination	Account type ("SAVINGS", "CHECKING", "DEPOSIT", "OTHERS")