Skip to main content

Fastoo Cross-Border Payments

Create Fastoo payouts through the standard LuxCore Payments API. Use the destination format for the recipient and track the payment through the usual status endpoint and webhooks.
Contact your account manager to enable the route and confirm supported countries, currencies, limits and fees for your merchant. Availability depends on your merchant configuration and the recipient’s eligibility.

Currency and Amounts

Use a currency enabled for your merchant and the requested payout route. These requests do not perform automatic currency conversion. Payment amount is an integer in minor units, according to the currency’s decimal precision. With two decimal places, 10000 means 100.00. See the balance guide for merchant balance information.

Create a Fastoo Payout

Use POST /api/v1/payments with X-API-Key. API v2 accepts the same payment body with its HMAC authentication. The method is bank_transfer, including wallet payouts; there is no public fastoo method code or separate merchant transfer endpoint. Required Fastoo routing fields:
Do not combine fastooDestination with bank_account, bank_code, account_type, beneficiary_tax_id, payid, payid_type or bsb, even as empty strings. payout.recipient_name is optional for a typed Fastoo destination. Send only the documented destination fields.

Fastoo Wallet

The following examples create the same 100.00 GEL payout intent. Use a GEL route enabled for your merchant and an actual recipient reference; the values shown are illustrative.
For kind: "wallet", send scheme and value using one of these forms: Use an identifier provided by the recipient. Valid syntax alone does not guarantee that the recipient can receive this payout.

Bank and SEPA Destinations

Replace the wallet payout with one of the following. The surrounding payment fields remain the same; choose the currency supported by the selected account and rail. For a saved Fastoo bank beneficiary:
For a saved SEPA beneficiary:
ibanAccountId identifies a saved beneficiary available for your payout route. Supply it as a decimal string from 1 through 2147483647; it is not a raw IBAN. Obtain the beneficiary identifier through your account manager. Inline SEPA beneficiaries are not accepted. For an inline bank beneficiary:
Use actual beneficiary data instead of these illustrative values. iban uses uppercase letters/digits, starts with a two-letter country code and has 15–34 characters. swift has 8 or 11 uppercase letters/digits. Name, bank and address are required nonblank strings of at most 200 characters; optional reference has at most 140. Do not send both bank and ibanAccountId or extra destination fields.

Payment Status and Retries

A successful creation response returns transaction_id and status. Creation does not mean that the transfer has completed. Read GET /api/v1/payments/{transaction_id} and process standard payment webhooks.
After a timeout or unknown result, preserve the original merchant_reference and any returned payment ID. Check the original payment or contact support before submitting a replacement. Reusing the same reference is not an unconditional retry guarantee. See creation outcome errors.

Incoming Payments

For an enabled incoming route, create a standard deposit or deposit_pp with method: "bank_transfer" and the configured currency. Do not include payout.fastooDestination on a deposit request. Display the instructions returned for that payment, including its exact amount and reference, to the payer. Track the result through the payment status endpoint and webhooks. Use the balance API to read your merchant balance. For an unconfirmed payment or unexpected balance, contact support with the payment ID and merchant reference.

Troubleshooting

See the payment error reference for standard errors. Share the payment ID, merchant reference and error code with support.