Skip to main content
A fiat payout debits USDC from your Tender merchant balance and delivers supported fiat currencies to a recipient. There are two methods: Internal — sends funds directly to a Nigerian bank account using the recipient’s bank code and account number. Anchor — routes funds through a third-party anchor integrated with Tender. You pass the anchor’s name as the method value. Tender currently supports MoneyGram as an anchor, with more to be added over time. Both methods use the same endpoint: POST /v1/api/payout/fiat.

​
Prerequisites

Authentication guide

These endpoints use Signed (HMAC) authentication — an HMAC-SHA256 signature is required on every request. See the authentication guide for code examples.

​
Internal bank transfer

1

Submit the payout

Call POST /payout/fiat with method: "internal", the asset, amount, and the recipient’s bank details.
2

Confirm initiation

A successful response returns the payout record with status: "pending".
3

Poll for completion

Call GET /payout/{id} until status is completed or failed.

Payout Fiat API reference

Full parameter list and interactive playground for both internal and anchor methods.

​
Anchor payout

Anchor payouts route funds through a Tender-integrated third-party provider. To initiate one, set method to the name of the anchor you want to use. The recipient’s required details vary by anchor.
MoneyGram is the only anchor currently available. Additional anchors will be listed here as they are integrated.

​
Available anchors

1

Submit the payout

Call POST /payout/fiat with method set to the anchor name and the recipient’s required details.
2

Redirect the recipient

The response includes a url. Direct your recipient to this URL to complete collection via the anchor.

​
Identifying the end user with reference

Anchor payouts accept an optional reference field — a stable identifier for the end user the payout is for. It is echoed back to the anchor as the payout’s merchant_reference for reconciliation, and for MoneyGram it also determines which MoneyGram consumer the payout is attributed to.
When you serve many end users through one Tender merchant account, pass a reference so each user maps to a distinct MoneyGram consumer — each with its own KYC record and its own transaction-limit window. Without a reference, every payout collapses into a single consumer for your merchant account, so all your users share one KYC identity and one aggregate limit.
The value must be stable per end user: reuse the same reference for the same person on every payout, and use a different reference for a different person. A per-transaction value (a new order or invoice id each time) would create a new MoneyGram consumer on every payout — re-triggering KYC and fragmenting limits. Omit reference (or set it to your own merchant id) to attribute the payout to your merchant account itself.

Payout Fiat (Anchors) API reference

Full parameter list and interactive playground for anchor-based payouts.

​
Payout status values

​
Error handling