# Payment gateway integration launch checklist

By JZ Tech · Documentation checked 13 September 2026

Guide: https://www.jztech.in/guides/payment-gateway-integration-checklist

Use this working test plan with your gateway's supported test environment. No merchant transactions were run for this reference. Mark a check complete only after recording your own evidence.

Gateway/API version: 
Merchant country: 
Environment: 
Reviewer: 
Review date: 

- [ ] **Account & market** — Confirm the merchant country, settlement account, currencies and payment methods with the provider.
  Evidence / reference: 

- [ ] **Credentials** — Keep test and live credentials separate; use a dedicated webhook secret or header where supported.
  Evidence / reference: 

- [ ] **Order creation** — Create an internal order and payment attempt before checkout; calculate the amount on the server.
  Evidence / reference: 

- [ ] **Payment matching** — Match the verified merchant or outlet, order reference, amount and currency to the intended attempt.
  Evidence / reference: 

- [ ] **Invalid notification** — Send a forged notification or invalid signature; confirm it cannot mark an order paid.
  Evidence / reference: 

- [ ] **Closed browser** — Close checkout before the return redirect; confirm the backend still resolves the payment.
  Evidence / reference: 

- [ ] **Duplicate delivery** — Deliver the same event twice, including concurrently; confirm one business action.
  Evidence / reference: 

- [ ] **Event order** — Deliver an earlier state after a later state; confirm payment status does not move backwards.
  Evidence / reference: 

- [ ] **Storage failure** — Interrupt durable storage before acknowledgement; verify the provider-specific recovery path.
  Evidence / reference: 

- [ ] **Worker restart** — Stop processing after receipt is stored; restart it and confirm the event can be completed.
  Evidence / reference: 

- [ ] **Fulfilment retry** — Retry fulfilment after a timeout; confirm stock, email and delivery actions are not duplicated.
  Evidence / reference: 

- [ ] **Missing callback** — Suppress a callback; resolve the pending payment through an authenticated status query or report.
  Evidence / reference: 

- [ ] **Refund lifecycle** — Check a partial refund and a full refund separately from payment, fulfilment and settlement.
  Evidence / reference: 

- [ ] **Mismatch** — Send a valid event for the wrong amount, currency or merchant; keep it out of fulfilment and flag it.
  Evidence / reference: 

- [ ] **Unknown event** — Add an unknown event type or JSON field; preserve compatibility without treating it as success.
  Evidence / reference: 

- [ ] **Release handover** — Record pending-payment alerts, reconciliation ownership, rollback steps and sanitized test evidence.
  Evidence / reference: 

## Provider documentation

- Razorpay: https://razorpay.com/docs/webhooks/validate-test/
- Hubtel: https://github.com/hubtel/hubtel-mobile-android-merchant-checkout-sdk
- Paystack webhooks: https://paystack.com/docs/payments/webhooks/
- Paystack verification: https://paystack.com/docs/payments/verify-payments/
- N-Genius: https://docs.ngenius-payments.com/reference/consuming-web-hooks
- N-Genius encryption: https://docs.ngenius-payments.com/reference/webhook-encryption-decryption-guide

## Release handover

Unresolved exceptions: 
Operational owner: 
Alert route: 
Recovery procedure: 
Rollback procedure: 

Share this checklist with your project team. Reference the guide URL when citing the resource.