Process cross-border remittance

curl -sS -X POST "$FLUIDE_BASE_URL/api/v1/payments/ecobank/remittance" \ -H "Authorization: Bearer $FLUIDE_ACCESS_TOKEN" \ -H "X-Fluide-Api-Key: $FLUIDE_API_KEY" \ -H "X-Fluide-Client-Id: fluide-developer" \ -H "Content-Type: application/json" \ -d '{}'

Authorizations

Authorization

string

header

required

Access token JWT. Use as Authorization: Bearer . In the API playground, paste the JWT only.

X-Fluide-Api-Key

string

header

default:fl_dev_your_key

required

Developer API key (fl_dev_...). Required on every API call with a machine access token.

X-Fluide-Client-Id

string

header

default:fluide-developer

required

First-party client audience. Must match the fluide_client_id claim on the JWT. Use fluide-developer for Connect.

Body

application/json

request_id

string

required

Unique request identifier

Example:

"2323V"

request_type

string

required

Type of remittance

Example:

"ECOBANKAFRICA"

receiverLastName

string

required

Receiver last name

Example:

"Kasumu"

sourceCountry

string

required

Source country

Example:

"NG"

senderNationality

string

required

Sender nationality

Example:

"GH"

senderPhoneNumber

string

required

Sender phone number

Example:

"07066690519"

destinationBank

string

required

Destination bank

Example:

"NG"

purpose

string

required

Purpose of transfer

Example:

"Travel"

receiverCcy

string

required

Receiver currency

Example:

"USD"

secureHash

string

required

Secure hash for request validation

Response

Remittance result

success

boolean

required

Whether the request succeeded

Example:

true

message

string

required

Human-readable outcome message (localized when i18n is configured)

Example:

"Operation completed successfully"

data

object

Endpoint-specific payload