A2A · Sandbox
Sandbox test environment
After onboarding starts, MerasPay provisions a sandbox credential with three test counterparty banks. Use these to run conformance without coordinating with real banks first.
Test BICs
| BIC | Bank | Behaviour |
|---|---|---|
| SBOXBANKADJ1 | Sandbox Bank A | Always accepts inbound, always succeeds outbound |
| SBOXBANKBDJ2 | Sandbox Bank B | Returns AC01 on creditor accounts ending in 9999 |
| SBOXBANKCDJ3 | Sandbox Bank C | Returns AM04 on amounts above 9,999,999 DJF |
Deterministic scenarios
| Trigger | Result |
|---|---|
Amount 1234 DJF | Always succeeds |
Amount 7777 DJF | Returns RJCT/NARR (generic decline) |
Amount 8888 DJF | Returns ACWP (high-value hold) — admin must approve |
Debtor name OFAC HIT | Returns ACWP (sanctions screen) |
| Reuse the same UETR | Returns the cached prior response (idempotency) |
Creditor account ending 9999 + BIC SBOXBANKBDJ2 | Returns RJCT/AC01 |
Resetting your nostro
Sandbox nostros at all three test banks are provisioned with 100,000,000 DJF target / 10,000,000 min / 200,000,000 max. To reset balances after running scenarios, hit the admin reset endpoint (sandbox env only):
POST /v1/admin/a2a/sandbox/reset
ℹ
JWS examples
Reference scripts that produce a properly-detached JWS over a sample body live in
docs/samples/a2a/ in the SDK repo. Languages: Node, Go, Python.