Skip to main content
Card payments let customers pay with Visa, Mastercard, and ArCa cards in hosted Checkout. To activate this option, obtain VPOS credentials from Ameriabank and connect them in Lynq Dashboard.

​
What you need from Ameriabank

Contact Ameriabank and request VPOS access for your merchant. The connection form requires: Ask Ameriabank which credentials apply to test and live processing. Do not reuse test credentials in the live Dashboard environment unless the bank explicitly provided them for live use.

​
Configure Card payments

Select the environment

Open Lynq Dashboard and choose Test mode or Live mode in the header.

Open Card payments

Go to Payment methods, find Card payments, and choose Configure.

Enter the VPOS credentials

Enter the Terminal ID, username, and password exactly as supplied. Choose Save and enable.

Confirm the connection

The Card payments entry should show as enabled. If you later disable it, Card stops appearing in new checkout sessions for that environment.
Credentials are encrypted when saved and secret fields are never displayed again. To update the connection, enter the username and password again along with the Terminal ID.

​
Customer flow

  1. The customer chooses Card in Lynq Checkout.
  2. Checkout collects the cardholder name, card number, expiry date, and security code inside the Lynq-hosted iframe.
  3. If the bank requires 3D Secure authentication, the SDK opens and completes that flow internally.
  4. Checkout returns a merchant-actionable result to your browser.
  5. Lynq sends payment_intent.succeeded to your webhook after successful completion.
Your application receives only non-sensitive card summary information such as the brand and last four digits. Raw card numbers and security codes are not exposed to your page.

​
Verify the setup

  • Create a Payment Intent using a secret key from the same environment.
  • Mount Checkout with the matching publishable key and client secret.
  • Confirm Card appears as an available method.
  • Complete a payment using the test details supplied for your VPOS setup.
  • Verify the payment in Dashboard and confirm your webhook processed the event once.

​
Troubleshooting

Confirm Card payments is enabled in the same environment used to create the Payment Intent. Then check that Checkout uses a publishable key from that environment.
Re-enter all values without leading or trailing spaces. If Ameriabank rotated the password, use the current Terminal ID, username, and new password together.
Let the customer retry from Checkout. Do not implement the 3D Secure redirect yourself; the SDK owns that flow.
For shared environment and connection rules, see Payment methods.
Last modified on August 8, 2026