Knowledgebase

Sandbox and Test Environments Print

  • 0

Developing without live data.

WHY A SANDBOX MATTERS

Callers cannot develop against live customers, money or messages.

WHAT IT SHOULD PROVIDE

The same interface Separate credentials Data that can be created and destroyed freely Predictable ways to trigger errors

WHY THAT LAST POINT MATTERS MOST

Testing failure handling requires a way to cause failures.

WHAT TO PROVIDE

Specific values that produce specific errors.

WHAT PAYMENT PROVIDERS DO

Test card numbers producing declines, timeouts and disputes.

WHY THAT IS THE MODEL TO COPY

It lets callers test everything that matters.

WHAT TO DOCUMENT

Every such trigger.

WHAT TO KEEP ALIGNED

Sandbox behaviour with production.

WHY

Divergence means code that works in testing fails live.

WHAT COMMONLY DIVERGES

Rate limits Validation strictness Response timing Which features exist

WHAT TO STATE CLEARLY

Any known difference.

WHAT TO NEVER DO

Let sandbox credentials work against production, or the reverse.

HOW TO PREVENT IT

Visibly different credential formats.

WHY

It makes the mistake obvious rather than silent.

WHAT TO PROVIDE FOR WEBHOOK TESTING

A way to trigger events on demand.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot