Verify Payment Gateway Connectivity Before Launch

Write down what the integration should connect to

List the approved gateway, account reference, environment, checkout domains, and intended transaction types. Verify the store receives configuration from the correct environment without printing credentials to a terminal, logs, or a support ticket. Check which provider tools confirm that account and environment.

Prove the connection with a complete test attempt

Use the provider’s test environment and documented test instruments. Create a sandbox order through the storefront and find the resulting transaction in the matching gateway view. If a webhook or status lookup is part of checkout, demonstrate that the transaction updates the original order.

Make failures diagnosable

Record whether the failure happened before the gateway call, during authorization, or while updating the order. Keep the non-sensitive correlation references and timestamp. Verify the corresponding provider record before deciding whether the configuration or the payment result needs correction.

Minimum launch evidence

• One approved sandbox transaction with matching order and gateway references.
• One documented decline visible in both the checkout experience and provider record.
• One refund or void tested using the workflow staff will use.