Test your integration

Test the same path your customers will use: order creation, Payment Intent creation, browser Checkout, provider flow, webhook verification, fulfilment, and Dashboard reconciliation.

Prepare Test mode

Before testing, confirm that Test mode contains:

A labelled secret key for your backend
A publishable key for your browser application
Every payment method you plan to offer, configured and enabled
A public HTTPS webhook endpoint with its signing secret installed
Logging that records Payment Intent and webhook event IDs without logging secrets

Core test scenarios

Scenario	Browser expectation	Server expectation
Successful Card payment	Checkout completes and reports `succeeded` or a pending transition before completion.	A verified success webhook marks the order paid once.
Card requiring authentication	The SDK owns the authentication UI and returns the customer to Checkout.	Fulfilment still waits for the success webhook.
Card declined or invalid	Checkout reports `requires_payment_method` with display-safe text.	The order remains unpaid and can accept another attempt.
Successful Idram payment	The SDK handles the wallet handoff and customer return.	The verified success webhook identifies the original order.
Customer closes the page	No irreversible browser-side action occurs.	A later webhook can still complete the order if payment succeeded.
Duplicate webhook	Customer-visible state does not change twice.	The event ID is recognized and fulfilment runs once.
Temporary webhook failure	Payment may look complete in Dashboard while delivery retries.	The receiver returns `5xx`, recovers, and processes a retry.

Use test payment details supplied by Ameriabank or Idram for their respective sandbox flows.

Checkout lifecycle tests

Show a loading state until onReady fires.
Make sure the page remains usable when onCheckoutError reports a retryable failure.
Destroy Checkout when the user leaves the payment step.
Create a fresh instance for a fresh Payment Intent.
Confirm only one Checkout is mounted at a time.
In an SSR application, confirm no Checkout instance is constructed during server rendering.
Test narrow and wide browser layouts and keyboard navigation around the hosted form.

Webhook tests

Send a Test mode event from Dashboard.
Confirm the receiver verifies Lynq-Signature against the raw body.
Confirm the event ID is stored with a unique constraint.
Replay the same request and confirm it returns 2xx without repeating fulfilment.
Send an invalid signature and confirm it is rejected.
Temporarily return 500 and confirm the delivery moves to retrying.
Restore the receiver and confirm a later delivery succeeds.

Reconciliation check

For each successful test, match all three records:

Your order by orderId
The Dashboard payment by Payment Intent ID
The webhook delivery by event ID

Testing is complete when every enabled payment method can update the correct order exactly once through a verified webhook, including after browser interruption and webhook retry.

Continue with the go-live checklist.

Start here

Payment methods

Build your integration

Test and go live

Reference

Resources

Prepare Test mode

Core test scenarios

Checkout lifecycle tests

Webhook tests

Reconciliation check

​Prepare Test mode

​Core test scenarios

​Checkout lifecycle tests

​Webhook tests

​Reconciliation check

Prepare Test mode

Core test scenarios

Checkout lifecycle tests

Webhook tests

Reconciliation check