Skip to main content
Lynq gives your application a server API for creating payments, a hosted browser checkout for collecting payment details, and signed webhooks for confirming completed payments. If you are integrating Lynq for the first time, follow the documentation in order. You will finish with a test payment flow that can be switched to live mode without changing its architecture.

Understand the payment flow

See which work belongs to your server, browser, Lynq, and payment provider.

Build your first payment

Create a test Payment Intent, mount Checkout, and verify the result.

Configure Card payments

Enter Ameriabank VPOS credentials in Dashboard.

Configure Idram

Add Idram merchant credentials and enable the method.

Go-live checklist

Complete every production-launch step.

​
What you will build

Your integration has two trusted boundaries:
  • Your server owns the secret API key, creates Payment Intents, verifies webhooks, and fulfils orders.
  • Your browser uses a publishable key and a Payment Intent client secret to mount hosted Checkout.
Lynq Checkout collects payment details, presents enabled payment methods, and handles Card authentication or Idram redirects without exposing those flows to your application code.
Do not fulfil an order from a browser callback alone. A verified webhook is the source of truth for irreversible fulfilment.
Need help? Email support@lynq.am.
Last modified on August 8, 2026