Scenarios
Force every outcome on testnet: Shield's KYC and the anchor's test cards.
Shield's KYC (sandbox)
Choose it with scenario in POST /v1/onboarding, or in the selector on the Onboard page.
| Scenario | Result |
|---|---|
approved | The leaf joins the allow-list: the user can transact |
rejected | Never inserted: the pool refuses the user's proofs and intents answer 409 |
blocked | Inserted, then block-listed: frozen until the ASP unblocks it |
The anchor's test cards (Lendara sandbox)
Any future expiry date and any 3-digit CVC work.
| Card | Outcome | Intent |
|---|---|---|
4242 4242 4242 4242 | Approved | completed |
4000 0000 0000 0002 | KYC rejected | error |
4000 0000 0000 9995 | Payment not received | expired |
4000 0000 0000 0077 | Approved after 30 s | completed |
Money edge cases
- A payment with someone's memo that the anchor does not report never funds anything: it waits for review.
- Late or second payments are kept for review, never applied automatically.
- Timeouts, dropped transactions and RPC lag never pay twice: the stored hash is checked first.