Payments
Connect Adyen
Cards and local payment methods on your quotes, through Adyen Pay by Link.
Overview
Adyen + TackQuote
TackQuote's Adyen integration creates a Pay by Link for a quote and sends the buyer to Adyen's hosted page, where whichever card and local payment methods your merchant account offers are presented. Adyen sits fourth in the checkout routing order — below Stripe, Authorize.net and Square — so a quote only reaches Adyen when none of those is connected. The quote is carried in Adyen's merchantReference, which is one of the fields inside Adyen's HMAC-signed notification payload, so a signed notification cannot be replayed against a different quote or a different amount. Only a successful AUTHORISATION settles a quote, and only when its signed amount and currency equal the stored quote total.
Connect an Adyen API key and merchant account, create a standard webhook in Customer Area, and quotes start routing to Adyen Pay by Link.
Before you start
What you'll need
- Adyen merchant account with the payment methods you want enabled
- API key for a web-service user (Customer Area → Developers → API credentials)
- Your merchant account code — not the company account
- A standard webhook and its HMAC key
- Live URL Prefix, for live mode only (Developers → API URLs)
Setup
How to connect Adyen
Create API credentials
In Customer Area go to Developers → API credentials, open your web-service user and generate an API key.Note your merchant account code
Pay by Link is created against a merchant account, not the company account. Copy the merchant account code exactly.Create a standard webhook
In Customer Area → Developers → Webhooks add a standard webhook pointing at the per-tenant URL shown in TackQuote Settings → Payments, then generate and copy its HMAC key.Connect and go live
Enter the API key, merchant account and HMAC key in Settings → Payments → Adyen. For live mode also paste the Live URL Prefix from Developers → API URLs. A quote routes to Adyen only when no higher-priority gateway is connected.
Capabilities
What you get
Pay by Link
Each quote gets its own Adyen-hosted payment link. Adyen decides which methods to show from your merchant account configuration — TackQuote does not restrict the list.
HMAC-Verified Notifications
Every notification item is verified independently against your webhook HMAC key. A batch is never trusted because one of its members verified, and a failed check is refused outright.
The Quote Is Inside the Signature
The quote reference, amount and currency are all part of Adyen’s signed payload, so a verified notification cannot be pointed at another quote or another amount without invalidating the signature.
Live Mode Fails Loudly
Adyen’s live endpoint is per-merchant, so live mode needs your account’s own URL prefix. Without it the connection is refused rather than quietly falling back to the test host and taking no real money.
FAQ
Adyen questions
Why does live mode ask for a Live URL Prefix?
Adyen’s live API endpoint is per-merchant — your account’s own prefix is part of the hostname, and there is no shared live host to fall back on. TackQuote refuses a live connection without it rather than silently using the test endpoint, which would look like a working connection while taking no real money.
Which Adyen events mark a quote paid?
Only AUTHORISATION with success true. Adyen emits several notifications per transaction — CAPTURE, REFUND and others — and those are verified, recorded as seen and then deliberately ignored. A refund issued in Adyen is not reflected back onto the quote.
What happens if Adyen redelivers a notification?
Nothing incorrect. Each notification is claimed once by its Adyen reference and event code together, so a redelivery is recognised as a duplicate and a quote cannot be paid or converted twice.