Skip to content

Sandbox

Pyng provides a sandbox environment for end-to-end integration testing. The sandbox mirrors production behaviour identically — same endpoints, same request and response shapes, same error codes, same state transitions, same SLA. The only difference is that settled debits do not transfer funds to the partner's actual business bank account.

URL - https://sample.pyng.com.au

Provisioning

Sandbox credentials, siteId values, and a sandbox Pyng customer identity for testing the signup flow are provided by your Pyng account manager during onboarding. Sandbox and production credentials are separate; tokens issued by one environment do not authorise requests in the other.

Behaviour

Every aspect of the API operates identically to production:

  • Authentication and scopes
  • The customer invitation, signup, and linking lifecycle
  • Batch submission, asynchronous processing, and status polling
  • All HTTP status codes, error codes, and LinkState / BatchState / RowState / FailureReason values
  • The 24-hour batch SLA and per-row settlement timing
  • Rate limits and Retry-After semantics

The only difference: row settlement does not move funds to the partner's production bank account.

Customer Sandbox Flow

Customers who follow a sandbox signupUrl complete signup through Pyng's sandbox identity flow rather than production. Once signup completes, the link transitions to linked and the customer is debit-eligible against sandbox batches. Sandbox customers cannot make real-world payments and do not appear in production reports.