E-commerce Multi-Currency Collections

Use this flow when your e-commerce business needs to accept payments from international buyers in their local currency and settle balances into one or more treasury wallets.

✅ Before you start

Complete these steps before you enable multi-currency collections:

1. Authenticate with the merged Login service and store the returned token and companyId.
2. Decide the currencies you want to accept and which corridors apply.
3. Create wallets for each collection currency you plan to receive into.
4. Issue local or global receiving details for each wallet, depending on the corridor.
5. Register webhook endpoints so you can reconcile inbound settlement events in real time.

📚 Use this page with the recipe

This guide explains when to use the multi-currency collection flow and the minimum sequence. For the implementation walkthrough, use the recipe:

E-commerce Multi-Currency Collections Recipe →

The multi-currency collection workflow

This use case follows a simple sequence:

1. Create the wallet for each collection currency.
2. Issue receiving details for that wallet using the supported local or global rail.
3. Display the exact sender instructions returned for that corridor to the buyer or hosted checkout flow.
4. Listen for inbound settlement webhooks and wait for each collection event to reach the completed state.
5. Reconcile the wallet credit against the order before releasing the goods or service.
6. Convert collected balances to a treasury currency when needed using FX Conversion or OTC.

What makes this use case different?

Unlike a single-currency checkout, multi-currency collections need to:

• present the correct local rail and sender instructions per buyer corridor
• reconcile inbound events against orders rather than just wallet credits
• support both holdable balances and auto-convert flows depending on currency

Where to go deeper

• Accounts
• Receive
• Integration Guide
• Currency Guides
• FX Conversion Guide

Troubleshooting

Next steps