Go-Live Checklist

Complete every item before switching to production.

Business sign-off

• KYC and merchant agreement complete — Merchant Signup & KYC
• Production settlement account confirmed
• DigetPay integration team approved go-live date

API configuration

• Production API key obtained and stored securely (secrets manager)
• Production base URL configured (https://api.digetpay.com/v1)
• Staging keys removed from production deployments

{
  "production": {
    "apiBaseUrl": "https://api.digetpay.com/v1",
    "headers": {
      "x-api-key": "FROM_SECRETS_MANAGER"
    }
  }
}

Payment flow

• Create Payment Link works with production credentials
• customerPhone sent on every create request
• successUrl and failureUrl point to your production domains (HTTPS)
• Customer can complete card payment on hosted checkout
• Apple Pay tested (phone provided at link creation)
• Status API returns correct state after payment
• Hosted or embedded integration tested on staging (if applicable)

Identifiers

• Backend stores gatewayTransactionId after successful payment
• Status and refund use gateway UUID, not session ID or numeric payment ID

Security

• API key never exposed in frontend or mobile client code
• All API calls use HTTPS
• Error handling does not leak API keys in logs
• Webhook signature verification enabled (if applicable)

Webhooks

• Production webhook URL registered (HTTPS)
• Handler returns 200 within seconds
• Idempotent processing by transactionId + type
• Webhook signing secret stored in secrets manager

Operations

• Support contact documented for payment failures
• Reconciliation process defined (order ID ↔ session ID ↔ gateway transaction ID)
• Refund policy and workflow documented internally

Sign-off