Lynq is in test mode. Live payments aren’t available yet: we’re working with banks and regulators to switch them on. Everything in these docs works in test mode today, so you can build and test your whole integration now.
Build an integration
Create a Payment Intent on your server
Your server creates the payment and its client secret with your secret key. See Payment Intents.
Mount Checkout in the browser
Hosted Checkout collects payment details inside your page. See Lynq.js.
Verify the success webhook
Fulfil the order only after a verified webhook confirms the payment. See Webhooks.
Go live
Once live payments are available, connect your payment methods and switch to live keys. See the go-live checklist.
How a payment works
Three rules hold across every page of these docs:- Secrets stay on your server. The secret API key and the webhook signing secret never reach the browser. The browser gets the publishable key and one Payment Intent client secret.
- The webhook decides fulfilment. The browser result is for customer-facing UI: browsers can close, lose connectivity, or be manipulated. Ship goods or mark an order paid only after a verified
payment_intent.succeededwebhook. - Test and live never mix. Keys, Payment Intents, payment-method connections, and webhook endpoints work only within their own mode.