Connect your Adyen account

Before you start

A store can take its payments on your own Adyen merchant account instead of a Whop business. Buyers are then charged on your Adyen account, never on LatchPay, and you are the merchant of record: payouts, refunds and chargebacks stay on your Adyen account under your agreement with Adyen.

• An active LatchPay membership and a connected Shopify store.
• An Adyen account with a merchant account for the store, and access to its Customer Area (start with the test Customer Area, ca-test.adyen.com).

Create a LatchPay API credential

LatchPay connects with one API key. Create a separate credential for LatchPay, so you can remove it on its own later.

1. 1

   Create a Web service user

   In your Customer Area go to Developers › API credentials › Create new credential and choose Web service user. Prefer a credential for the merchant account of this store, not for the whole company.

2. 2

   Tick exactly these roles

   • Checkout webservice role
   • Checkout encrypted cardholder data
   • Merchant PAL webservice role
   • Management API—Account read
   • Management API—Webhooks read and write

   Recommended:

   • Merchant Recurring role (subscriptions and one-click offers)
   • API tokenise payment details (to remove saved cards)
   • API dispute management role (to answer disputes from LatchPay)
   • Management API—Payment methods read and write (Apple Pay on your own checkout domain)

   Do not tick these two

   Management API—API credentials read and write, and Management API—Users read and write. With them a leaked key could create new keys or Customer Area users for your whole company, so LatchPay refuses a key that holds either.
3. 3

   Leave Allowed IP addresses empty

   LatchPay's servers have no fixed IP address, so a key with an IP allow-list would fail on every call and is refused. LatchPay adds the allowed origins (the checkout's web addresses) itself.

4. 4

   Generate the API key and copy it

   Adyen shows the key once. Copy it; you paste it into LatchPay next.

5. 5

   Recommended: additional data

   Under Developers › Additional data, switch on Card summary, Expiry date and Issuer country, and the recurring details, so orders show the card's last four digits and saved cards arrive at once.

Connect Adyen

1. 1

   Choose Adyen for the store

   In the wizard's payment step, choose Adyen. In the dashboard, open the Adyen page.

2. 2

   Paste the API key

   Paste the key into the API key field and press Connect Adyen. LatchPay checks the key with Adyen (a few seconds). Test or live is detected from the key. The key is stored encrypted and never shown again.

3. 3

   Fix what the page names, if anything

   When a role is missing or one of the two roles above is ticked, the role list on the page marks it. Change the credential in your Customer Area, save, and paste the key again.

Choosing the merchant account

When the key reaches more than one merchant account, LatchPay asks which one the store uses; the account whose web address matches your store is preselected. The choice expires after 15 minutes; then paste the key again. A key for one merchant account only is safer, and the Adyen page says so while the key reaches several.

What LatchPay sets up for you

• A standard webhook on the merchant account, pointing at LatchPay, with its own HMAC key: payments, refunds and disputes reach LatchPay through it.
• The allowed origins on the API credential: LatchPay's checkout and each custom checkout domain of your stores.
• Apple Pay on your own checkout domain, when the key holds the Payment methods role.

The Adyen page shows each of them with a check or a cross. Check again asks Adyen anew; Send a test webhook makes Adyen send test events and shows how many reached LatchPay.

Test and live

A test key and a live key are two separate connections, each with its own card on the Adyen page. Start with a test key and a development store. When your live account is ready, paste a live key and press Use for this store on the live card. Test orders reach Shopify like real ones, so use a development store for tests.

Capture should be Immediate

LatchPay writes the Shopify order when a card payment is authorised. Set card capture to Immediate under Account › Settings in your Customer Area. With manual capture or a delay of some days, the money moves later or only after you capture in the Customer Area; the Adyen page shows a warning then. Klarna and other pay-later methods are captured right away.

Payment methods

The payment box shows the methods enabled on your Adyen merchant account that fit the order: cards, iDEAL, Bancontact, EPS, Klarna, Riverty, Trustly, BLIK, MB WAY, Swish, Twint, Vipps, MobilePay, Przelewy24, PayPal and more. Here you can only hide methods. PayPal starts hidden: switch it on in Adyen and then in the Payment methods card. Pay-later methods appear once the buyer's address is filled in.

Apple Pay and Google Pay

• Apple Pay and Google Pay show inside the payment box on Adyen stores, not above Contact.
• Apple Pay needs your own checkout domain (Settings › Checkout domain); it does not show on LatchPay's shared checkout address.
• Google Pay in live needs your Google merchant ID set up at Adyen.

Refunds

Refunds made from LatchPay or in your Customer Area show on the order and reach Shopify once Adyen reports them. The Orders page links each payment as Refund on Adyen.

Disputes

Adyen sends disputes to LatchPay as they happen; they show on the Chargebacks page. With the API dispute management role you answer a dispute there: pick a defense reason, upload the documents it asks for (PDF, JPG or TIFF up to 2 MB each) and send the defense, or accept the dispute. Without the role, respond in your Customer Area.

Subscriptions and one-click offers

Subscriptions and one-click post-purchase offers charge a saved card on your Adyen account. They need the Merchant Recurring role (and API tokenise payment details for removing saved cards). Only cards are saved; wallets and other methods are not.

Warnings on the Adyen page

• Capture delay: set card capture to Immediate (see above).
• This key can reach several merchant accounts: create a credential for this store's merchant account only and replace the key.
• This key also holds a role LatchPay does not need: remove it from the credential, or create a separate LatchPay credential with the roles above.

Fees

Adyen's own fees apply on your Adyen account. LatchPay adds nothing to the payment: your LatchPay plan and the weekly usage fee stay exactly the same, billed through Whop to the card on your membership, whatever provider a store uses.

Replacing the API key

When you rotate the key in your Customer Area, the old key keeps working for 24 hours. Within that time press Replace API key on the Adyen page and paste the new key. The webhook stays; LatchPay sets the allowed origins on the new credential again.

Disconnecting and switching

• Disconnect on the Adyen page removes LatchPay's webhook and the allowed origins it added, and deletes the stored key. Every store on that merchant account stops taking payments until you connect again; refunds and disputes of earlier orders are then handled in your Customer Area.
• Also delete the LatchPay API credential in your Customer Area. Apple Pay domains stay registered; they do no harm.
• Switching a store between providers only changes where new payments go. Checkouts already paying finish on their own provider, and refunds of earlier orders stay on the provider they were paid on.