Skip to main content
Move to live mode only after the complete Test mode flow passes. Test and live resources are separate, so launch is a controlled replacement of credentials—not a different integration architecture.

​
1. Payment-method readiness

  • Choose Card payments, Idram, or both.
  • Obtain live Ameriabank VPOS credentials for Card and/or live merchant credentials from Idram.
  • Switch Dashboard to Live mode.
  • Enter the live credentials under Payment methods and enable each method.
  • Confirm the Dashboard reports Card as ready for live checkout.

​
2. Production credentials

  • Create a labelled live secret key for the production backend.
  • Create a labelled live publishable key for the production frontend.
  • Install the secret key in production secret storage.
  • Install the publishable key in browser-safe production configuration.
  • Confirm no test key remains in the production deployment.
Do not revoke test keys just because you are launching. Keeping a working Test mode integration gives you a safe place to verify future changes.

​
3. Server integration

  • Create Payment Intents only from trusted server-side order data.
  • Send a stable idempotency key for each create attempt.
  • Return only the Payment Intent ID and client secret to the paying browser session.
  • Keep secrets, client secrets, and provider credentials out of logs.
  • Store the Lynq Payment Intent ID with your order.

​
4. Browser integration

  • Use the live publishable key with live Payment Intent client secrets.
  • Pin the Checkout SDK to the version you tested.
  • Register result and error handlers before mounting.
  • Show clear loading, pending, retry, and submitted states.
  • Destroy Checkout when the payment page unmounts.
  • Never fulfil from a browser callback.

​
5. Live webhook

  • Create and enable a live HTTPS webhook endpoint.
  • Save its signing secret in production secret storage.
  • Verify the signature against the raw body and enforce replay tolerance.
  • Deduplicate event IDs in the same database transaction as the order update.
  • Compare event amount, currency, and order ID to your stored order.
  • Return 2xx only after durable processing.

​
6. Production verification

Deploy the production integration

Confirm the release contains the live publishable key and the server has access to the live secret key and signing secret.

Create a small live order

Use an order you can identify and reconcile. Avoid testing with a customer’s real order.

Pay with each enabled method

Complete a small Card payment and/or Idram payment using the customer-facing production page.

Reconcile all records

Match the order, Payment Intent, provider method, browser result, webhook event, and fulfilment record.

Confirm operational ownership

Make sure the team knows where to monitor payments, inspect webhook deliveries, rotate credentials, and contact support.

​
7. After launch

  • Watch the first production payments and webhook deliveries closely.
  • Investigate pending or failed deliveries before they exhaust retries.
  • Keep Test mode working for release validation.
  • Rotate any credential that may have been exposed.
  • Review Checkout SDK release notes before upgrading.
Launch is complete when every enabled live method has produced a real payment whose verified webhook updated the intended order exactly once.
Last modified on August 8, 2026