One payment, one account, no guesswork

Know exactly who paid, every time — with a one-time account for each payment.

DSGPay Collections generates a dynamic, single-use virtual account for each order, invoice, or customer, across 12 markets. Your customer pays by ordinary local transfer, and because the account exists for that one payment, it's matched automatically — no reference codes, no payment screenshots, no manual reconciliation.

Start collecting

12 markets

Single-use virtual accounts

Automatic reconciliation

Markets where you can collect with one-time accounts

1:1

One virtual account for each order, invoice, or customer

Auto

Payments matched without manual reconciliation

On demand

Accounts generated from your platform via the GraphQL API

Why merchants use DSGPay Collections

Reconciliation that takes care of itself.

When hundreds of customers pay into one account, working out who paid for what becomes a daily job. Collections removes the question entirely.

Matched by design

Each account exists for one payment, so a deposit identifies itself. No reference fields to parse and no amounts to eyeball.

Generated on demand

Create an account at checkout, when an invoice is raised, or when a customer signs up — through the API or from OneWeb.

Local rails in 12 markets

Customers pay the way they already pay at home, on domestic transfer systems and in their own currency.

Named in your business

Accounts carry your business name, so customers see who they're paying and trust the details.

Know the moment it lands

Get notified as soon as a payment arrives, so orders can be released or services switched on without waiting.

Settle the way you want

Hold collected funds in local currency, convert them, or use them for payouts in the same market.

What Collections is built for

When volume is high and every payment has to be matched.

1. E-commerce checkout

Show a one-time account at checkout and confirm the order as soon as it's paid.

2. Invoice collection

Put a unique account on every invoice so receivables reconcile themselves.

3. Platforms and marketplaces

Give each buyer, seller, or user their own account for top-ups and payments.

4. Bookings and deposits

Take deposits from travellers and customers, with each payment tied to its reservation.

Collections or local accounts?

Single-use for volume, reusable for relationships.

Collections

A new account for each payment

Best for high-volume, one-off payments where automatic matching matters most — checkouts, invoices, and bookings.

Local Named Account

The same account, every time

Best for repeat customers who save your details and pay regularly — distributors, tenants, and subscribers.

Same account, every way you work

Run Collections from OneWeb, DMA, or the API.

No separate onboarding. Collections sits on the same DSGPay infrastructure as your named accounts, payouts, and FX.

Web

DSGPay OneWeb

Generate accounts for invoices and watch payments arrive from your browser.

Mobile

DSGPay DMA

Get notified the moment a payment lands, wherever you are.

API

DSGPay GraphQL API

Create single-use accounts at checkout and receive payment events via GraphQL subscriptions.