Skip to main content
The addresses you get back from registration are the whole product surface. Understanding what they are makes the rest of the API obvious.

One account, two addresses

Every registered bank account has two addresses that pay it: one for Solana and one for the EVM chains. Send to whichever matches the chain your user is paying from. Both pay out the same way, to the same bank account. The Solana address is a program-derived address computed from the account’s own identity: its account number, its bank code and its region. Nothing random is involved, and no pool of pre-generated addresses is drawn from. The EVM address is a wallet Paj issues for the bank account when it is registered and holds on its behalf. An EVM address is the same on every EVM chain, so this one address receives on all of them, and Paj watches it on each.
Only send to evmAddress on the EVM chains listed above. The address exists on every EVM network, so a wallet will let your user send on, say, Polygon or Arbitrum. Paj does not watch those chains, so a transfer there is not paid out.
TON has no bank account address. Paying a bank account from TON goes through an offramp order instead, which issues a funding address on whichever supported chain you name. Two properties hold for both addresses, and both simplify your integration:

Stable

A bank account’s addresses never change. Store them once; they will not rotate or expire, and you never have to refresh them.

Shared

The addresses belong to the bank account, not to your business. If another Paj integration registered the same account first, you get the addresses it already has.
evmAddress is issued during registration, but it can be missing from the response for a short time after it if issuing it was delayed. The Solana address is always there. If you need the EVM address and it is missing, look the account up again with GET /pub/v2/bank-account a little later.
Both addresses are only as safe as the account number your user gave you. Always show the accountName returned by registration and have the user confirm it — a typo produces valid addresses that pay a stranger’s bank account.

What happens after a deposit

Nothing is required from your API integration once you have shown the address. Paying it is the instruction, on either chain:
1

Funds land

A deposit arrives at the address — a real, separate on-chain balance. Paj’s listener picks it up within seconds of the transaction confirming on its chain.
2

Swept into the pool

The balance is moved on-chain into Paj’s treasury and an offramp transaction is opened against the bank account it belongs to.
3

Value check

USDC/USDT pays out directly. Non stable token is priced for its USD value, so senders are not restricted to a single mint.
4

Paid out

Naira is disbursed to the bank account through the banking rail at the prevailing offramp rate. The on-chain legs take seconds; the fiat leg dominates the end-to-end time.

Tracking a deposit

Because paying the address creates no order, there is nothing to poll. To follow a transfer through these steps, subscribe on the deposit socket with its Solana signature or its EVM transaction hash. You get its current state when you subscribe, then an update at each step, through to the naira payout.
You can subscribe as soon as the transfer is sent, before Paj has seen it.

Amounts and rates

The rate applied is the offramp rate in effect when the deposit is observed, not when you last called GET /pub/v2/rate. If you quote a figure to a user before they send, treat it as indicative — see Rates. There is no per-deposit registration step, so there is also no amount to commit to in advance. A user can send any amount, any number of times, to either address. Deposits worth less than 0.40 USDC are too small to pay out and are not picked up.

Reversing the lookup

When you see a deposit on-chain and want to know whose it is, pass the address to GET /pub/v2/bank-account. It accepts either address, and an EVM address in any letter case. This is the same mapping in the other direction, and it is the intended way to attribute an on-chain event back to one of your users.