FXBO announced a broker-payment partnership with Luxon Pay on 29 October. The integration is available to eligible FXBO brokerages, subject to Luxon’s standard onboarding and approval process, with support from both teams. The statement does not specify when the connection first went live.[1]
FXBO’s partner directory describes the connection as live and lists merchant accounts that can hold and convert multiple currencies, with settlement routes including SEPA and SWIFT. It advertises support for more than 38 currencies and fee-free trader withdrawals. Those descriptions need to be read alongside the implementation terms and Luxon’s separate merchant-payment records.[2]
Availability depends on the implemented connection
FXBO’s PSP terms say its directory describes providers’ general coverage; a particular region or currency may still need additional integration work. Existing connections can also require updates when a provider changes its system, potentially at additional cost. A directory entry therefore does not establish that every advertised currency is enabled for every broker.[3]
Luxon’s setup guide describes testing before production activation, with a merchant identity, authentication keys and callback addresses configured for the business. Its two-step deposit flow gives the merchant customer details to validate before approving or declining payment. Its separate OneClick flow requires a billing agreement authorised by the customer. These are documented Luxon capabilities; the partnership announcement does not specify which flows each FXBO deployment enables.[4]
A submitted request is not a completed payment
How Luxon identifies payment progress
| API status | Documented meaning |
|---|---|
| PENDING | The transaction has been initiated; the status is intermediate.Source 5 |
| PROCESSING | The transaction has been accepted and is being processed; completion remains outstanding.Source 5 |
| PROCESSED | Processing completed successfully; this is a final status.Source 5 |
| REJECTED, FAILED, CANCELLED or EXPIRED | Final outcomes that do not represent successful completion.Source 5 |
That distinction matters when updating a trader’s available balance or investigating a withdrawal. Luxon documents failures arising from risk limits, anti-money-laundering checks, currency problems and account mismatches. Accepting a request into the processing system does not resolve those checks.[5]
The completion callback carries the transaction identifier, customer reference, amount and a merchant fee field. This allows the payment record to be reconciled with the broker’s records. A fee-free claim aimed at the trader does not establish a zero-cost merchant arrangement: Luxon’s API explicitly accommodates a charge to the merchant, without publishing a universal tariff in this documentation.[6]
Sources & further reading
- FXBO and Luxon Pay Join Forces to Revolutionize Payment Solutions Within CRM Technology FXBO / EIN Presswire via Technology Report Cyprus · 29 Oct 2026 · Accessed 30 Oct 2026
- Luxon Pay integration and merchant capabilities FXBO · Accessed 30 Oct 2026
- Payment-provider integrations: PSP terms of use FXBO · Accessed 30 Oct 2026
- Getting Started: merchant setup and payment flows Luxon Pay · Accessed 30 Oct 2026
- Transaction statuses and completion conditions Luxon Pay · Accessed 30 Oct 2026
- Webhooks: payment confirmation and fee fields Luxon Pay · Accessed 30 Oct 2026