Payments
adyen.com:AccountService
Adyen sandbox and mock API
This API is used for the classic integration. If you are just starting your implementation, refer to our [new integration guide](https://docs.adyen.com/marketplaces-and-platforms) instead. The Account API provides endpoints for managing account-related entities on your platform. These related entities include account holders, accounts, bank accounts, shareholders, and verification-related document Writes persist, data moves on a schedule and every change can fire a signed webhook.
- Operations
- 20
- Collections
- -
- Event types
- -
example request
curl https://your-adyen.slurry.io/ \
-H "Authorization: Bearer slurry_sim_..."Your simulation gets its own hostname, key and IP allow-list. Built from API version 6.
What gets simulated
Collections, relationships and state machines are worked out from the spec when you start the simulation.
- State. Creates, updates and deletes persist and show up in later reads.
- Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
- Webhooks. Every change emits a signed, retried event.
- Failure. Per-endpoint errors, latency and chaos rules, on demand.
Operations
First 12 of 20.
- POST/checkAccountHolder
- POST/closeAccount
- POST/closeAccountHolder
- POST/closeStores
- POST/createAccount
- POST/createAccountHolder
- POST/deleteBankAccounts
- POST/deleteLegalArrangements
- POST/deletePayoutMethods
- POST/deleteShareholders
- POST/deleteSignatories
- POST/getAccountHolder