Skip to main content

​
Non-production vs production

Use staging or other non-production environments to integrate without touching real payees or live verification traffic. In non-production, test BSB codes drive predictable bank-name and account outcomes so you can automate checks and verifications safely. Production uses live data sources and real contact flows. Treat API keys and webhooks as environment-specific: never share production keys with sandbox tools.

​
Test bank account data

The Test bank accounts page lists BSBs that simulate “no account,” “closed,” name mismatch, close match, and exact match. Use these whenever you need deterministic responses while building check and verification flows. Where ABA uploads parse per-line BSB and account numbers, the same test BSB semantics apply in non-production so batch flows stay testable.

​
Webhooks in development

Point webhook subscriptions at a tunnel or dev gateway (for example ngrok, Cloudflare Tunnel, or a shared staging URL) so webhook deliveries reach your machine. Verify your handler returns quickly and treats idempotency and retries like production.

​
Rate limits and list behavior

Bulk or polling-heavy tests should respect rate limiting. For large result sets, use pagination and filtering as documented for each list endpoint.

​
Full integration path

Follow the API quickstart end-to-end in a non-production environment before going live.