Developer guide
Test the workflow before real money.
Prepare the success, failure and retry scenarios your integration would need to handle. Any sandbox access, test credentials and supported scenarios must be agreed with the team.
Prepare your test environment.
- Access and scope
Confirm supported domains, permissions and test credentials with the platform team.
- Test data
Use the fixtures and test values supplied for the environment. Do not use real customer data in an unapproved test setup.
- Environment boundaries
Keep test credentials, configuration and records separate from production. Confirm the documented differences between environments.
Test more than the happy path.
If a test environment is agreed, request its credentials, fixtures and specification. Include credit-review exceptions, unmatched repayments and repeated events in the evaluation.
- Valid and invalid inputs
- Test success, validation errors, missing permissions and unsupported operations.
- Interruptions and retries
- Test timeouts, repeated requests and recovery without duplicate financial actions.
- Events and reconciliation
- Confirm how your integration handles repeated or delayed events and verifies the final operation state.