Add Global Collections to Your Domestic Payments Business

Use this flow when you want to keep your domestic payments product and add inbound global or multi-currency collection capabilities that settle into Verto wallets.

✅ Before you start

Complete these steps before you implement the collection flow:

Confirm whether your business fits Atlas for Fintech or Atlas for Platforms based on your licence status and customer model.
Choose the currencies and rails you want to support for inbound collections.
Create the wallet that will receive the inbound funds.
If you are issuing receiving details for downstream customers, create and approve the relevant sub-account first.
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 collection flow and the minimum sequence. For the implementation walkthrough, use the recipe:

Add Global Collections to Your Domestic Payments Business Recipe →

🧭 Which model usually fits?

Model	Use it when	Operational pattern
Atlas for Fintech	You are a licensed domestic provider extending your treasury or collection footprint.	Issue accounts into your own wallet context and reconcile inbound funds directly.
Atlas for Platforms	You need to issue receiving details for downstream customers under your programme.	Create the customer context first, then issue accounts and reconcile collections in that scoped context.

The global collections workflow

This use case follows a simple sequence:

Create the wallet for the currency you want to collect.
Issue the account details for that wallet using the supported local or global rail.
Display the exact sender instructions returned for that corridor in your UI or operational workflow.
Listen for inbound settlement webhooks and wait for the collection event to reach the completed state.
Reconcile the resulting wallet credit into your application before you release funds for treasury or payout use.

What makes this use case different?

Unlike payout-first flows, this pattern starts with collection infrastructure:

accounts define where funds should arrive
receive events confirm when funds have actually settled
wallet reconciliation determines when balances become operationally available

Optional: Sweep, convert, or route funds onward

Once the inbound balance is confirmed, you can move the funds into your treasury workflow.

Depending on your setup, that can mean sweeping balances, converting currency, or using the wallet as the funding source for later payouts.

Where to go deeper

Use the product guides when you need implementation detail for a specific step:

Troubleshooting

Issue	What to check
Account cannot be issued	Confirm the wallet exists, the currency is supported, and your account is approved for that corridor.
Funds do not auto-allocate	Check whether the receiving account is pooled and whether the payer included the required reference value.
Inbound webhook does not update your balance	Update your internal ledger only after the receive event reaches the completed state, and deduplicate webhook deliveries by event ID.
Wrong customer context receives the funds	Verify whether the account was issued in the correct master or sub-account context.

Next steps


Accounts → Issue and manage the receiving details behind the collection flow.	Receive → Handle inbound settlement events and wallet reconciliation.

Talk to Verto

Get help with authentication, receive flows, wallets, FX conversion, payouts, or Atlas platform setup.

Plan your go-live

Review the requirements you need before moving your integration into production.