Test data
The following sender data can be used to test different compliance and transaction validation scenarios:
| Parameter | Value | Result | Compliance Status | Payout Status |
|---|---|---|---|---|
| address.zipcode | 99999 | Transaction will be REJECTED | Rejected | Cancelled |
| phoneNumber | +14155550000 | Transaction will be REJECTED | Rejected | Cancelled |
| firstName + lastName | BLOCK LIST MATCH | Transaction will be REJECTED | Rejected | Cancelled |
| firstName + lastName | OFAC MATCH | Transaction will be put ON HOLD for further verification | Pending | Pending |
| firstName + lastName | JULIO SOLANO | Compliance hold at the payout network (PayoutHold) | Pending | Processing |
| address.zipcode | 96738 | Payout-network rejection when beneficiary data is incomplete | — | Failed |
Document numbers. Sender creation format-checks every declared document and verifies the number against the Inyo KYC service, so an invented number can fail the request before anything is persisted. Sandbox accepts reserved document numbers that return a chosen valid verdict, covering driver's licences, passports and identity cards.
For end-to-end lifecycle testing — forcing 3DS completion, ACH settlement, payout delivery, holds, and voids — see Sandbox Testing.