You may create counterparties in your sandbox with the same data you would use in production. All routing details on external accounts are run through the exact same validations that are run in production.
Your sandbox will also be automatically seeded with counterparties that enable you to quickly create and test payments and workflows. These counterparties can be used to simulate successful and [returned](🔗) payments.
# Default Counterparties
|Will result in successful ACH, Wire, Check and RTP payment orders.
|Voldemort (ACH/Wire Return) - R01 Insufficient Funds
|Will result in an ACH return with code R01.
|Snape (ACH/Wire Return) - R03 No Account/Unable to Locate Account
|Will result in an ACH return with code R03.
|Lucius (General Failure)
|Will fail ACH, Wire, and RTP payment orders.
|Bellatrix (Check Failure)
|Will fail Check payment orders.
|Draco (EFT Return) - 901 NSF
|Will result in an EFT return with code 901.
You can edit these counterparties, which may change their behavior for future payment orders. We recommend not modifying these counterparties and instead prefer creating new counterparties to test your workflows.
# Creating Default Counterparties Manually
If you do not have these default Counterparties already, you can create them through the API below.
**Note**: Remember to use your Sandbox API key to create these Counterparties.