Test a complete payment flow
Sandbox readiness, external provider execution and webhook delivery are separate pieces of evidence.
Use an explicit test scope#
Use SANDBOX in every create request and select an amount within the intended capability limits. The API base URL is shared; the request mode and provider configuration determine the environment.
Connections and Test Center readiness identify local configuration blockers. A dry-run does not create a transaction or call the provider. A successful credential check is not a completed payment.
Acceptance checklist#
- Confirm a supported payment reaches SUCCESS, then verify credited amount/currency and the merchant webhook.
- Exercise a provider-supported decline and confirm that the order remains unpaid.
- Observe a delayed initiation: CREATED without redirectUrl, then PROCESSING or a terminal result.
- Retry direct create with the same persisted idempotency key and confirm 409 without creating another logical order.
- Send duplicate webhook deliveries to your receiver and confirm exactly one business side effect.
- Test expired/abandoned checkout and changed method eligibility.
- For supported capabilities, test overpayment, underpayment and a payout with defined expected results. Mark unavailable scenarios as unsupported, never as passed.
Read the result in context#
A test belongs to its merchant, provider, region, operation, method, currency and amount. Configuration changes can make earlier evidence stale. Re-run the relevant test after changing credentials, bindings, limits, approval or delivery configuration.
Startbutton Sandbox has been exercised through a native payment checkout. That result does not certify all Startbutton methods, a payout capability, another merchant or Live processing.
