Troubleshoot wallet payments

Use this article when Apple Pay or Google Pay does not appear in the checkout, disappears after a domain change, or fails during payment.

Wallet buttons depend on more conditions than other payment methods: the payment provider must support the wallet, the domain serving the checkout must be verified for wallet payments, and the customer's device and browser must support the wallet. Work through the checks in order.

Check provider support first

Not every payment provider integration offers every wallet. Before checking domains or devices, confirm that your provider supports the wallet in the payment methods matrix in Payment setup overview. If the provider does not list the wallet, no domain or browser change will make it appear.

Lynck express checkout in the online shop

When Lynck is connected and Apple Pay or Google Pay is active for the account, eligible customers see the wallet's official branded button in the cart. Available express options appear in this order: Apple Pay, Google Pay, PayPal, then Amazon Pay. A wallet button is omitted when its provider SDK reports that the customer's device, browser, account, country, or currency is not eligible. The regular checkout action remains available.

Selecting Apple Pay or Google Pay opens the provider-managed wallet sheet. Wallet authorization may return an email address and relevant billing or shipping address data. KORONA Event imports those values only when the online shop's checkout settings allow them. Separate first and last names are not guaranteed wallet data, and KORONA Event does not split the full recipient name from an address into those fields. The wallet may not return every required field, and some fields—such as a telephone number, checkout questions, or required consent—are not guaranteed wallet data. The express review shows the imported contact details and, when needed, the delivery address as a summary. Customers complete only missing required fields and the required consent checkboxes before confirming payment. Edit all details opens the full form for corrections or optional details. Back to Express review returns to the compact view and keeps their changes. Customers can expand View order items to check individual items; the order total and payment button remain visible. Shipping details and order-specific questions are still required when the order needs them.

Check the wallet domain setup

1. In the back office, open Admin > Payment.
2. Scroll to the Wallet domain setup section. It lists each shop domain with its Domain, Apple Pay file, Status, and Details.
3. Check the Apple Pay file selection for the affected domain. The options are Stripe, PayPal, Lynck, and Custom upload. Stripe, PayPal, and Lynck serve their verification files automatically; Custom upload requires you to upload a domain association file yourself.
4. Check the Status column. KORONA Event tracks Stripe domain registration, but does not track registration in Lynck. For Lynck, File ready means that the bundled Lynck file is available; it does not confirm domain registration. Action required can indicate a different file source. For your own custom domain, follow the custom-file upload instructions rather than replacing your provider's file with the bundled Lynck file. Confirm that the uploaded file is reachable and finish registration in Lynck. When Lynck Apple Pay is not active and the file source is Stripe, the status shows Active, Syncing, Failed, Disabled, or Not connected when no Stripe account is connected.
5. For a Stripe Failed status, read the Details column for Stripe's error message before contacting support.

If the Wallet domain setup section is not visible for your account, ask KORONA Event support whether wallet domain management is enabled for your setup.

Register a Lynck domain for Apple Pay

Complete these steps for every domain that displays the Lynck Apple Pay Express button:

1. In Wallet domain setup, prepare the file for the domain: select Lynck for a standard KORONA Event shop domain, or download and upload the provider's file for your own custom shop domain. Follow Set up your domain for Apple Pay for the complete steps.
2. Open https://[YOUR-DOMAIN]/.well-known/apple-developer-merchantid-domain-association in a browser and confirm that the verification file is reachable over HTTPS.
3. Sign in to the Lynck merchant area and open Settings > Apple Pay > Web, Hosted Pages & Subscriptions.
4. Enter the domain and select Register.

KORONA Event serves the selected Lynck verification file, but it does not register the domain with Lynck or track that registration's status. Check the Lynck merchant area when the file is reachable but Apple Pay is still missing.

Prepare Lynck Google Pay for production

Google Pay Express is displayed on your online-shop domain. Before using it with live payments, your organization needs a Google Pay business profile, an approved website integration, and production access. A Google Pay button that works with Lynck test credentials does not confirm that the live integration is approved.

1. Follow Google's production integration guide to complete the business profile, accept the Google Pay API terms, add the online-shop website integration, and submit it for approval.
2. When Google provides the merchant ID, copy it from the Google Pay & Wallet Console. If First Cash or Lynck has already arranged onboarding, check their confirmation email or ask your onboarding contact for this ID before creating another setup. This is the Google merchant ID, not the Lynck or First Cash merchant ID.
3. In the KORONA Event back office, open Admin > Payment, select Lynck, and switch to Live Credentials.
4. Enter the ID in Google Pay Console Merchant ID. Google Pay becomes available under Activated payment methods only after this field contains a merchant ID. Select Google Pay, then save the Lynck settings.
5. Ask your Lynck onboarding contact or Lynck support to confirm that Google Pay Express is enabled for the live Lynck merchant and store and uses the same Google merchant ID.

Lynck may coordinate parts of the Google Pay onboarding for your account. Confirm with Lynck which steps they complete. KORONA Event stores the merchant ID used by the online shop, but it does not create the Google Pay business profile, request production access, enable Google Pay at Lynck, or track those external approval states. See the Lynck API documentation for Lynck's current Google Pay requirements.

Upload or replace a custom Apple Pay file

Only needed when the Apple Pay file source is Custom upload:

1. In the Wallet domain setup row, select Upload file (or Replace file when a file exists).
2. Select the original domain association file from your payment provider. It must be plain text or a generic binary download (octet-stream), 100 KB or smaller. Keep its contents unchanged.
3. Select Save file and confirm the row shows the uploaded filename.

The downloaded file ends in .json and cannot be selected

A filename ending in .json does not by itself tell you what the file contains. Some domain association downloads contain the provider's verification text even when saved with this extension. KORONA Event's upload currently rejects files identified as JSON.

1. Keep the original download. Show filename extensions in your file manager so you can see the complete name. In Windows File Explorer, use View > Show > File name extensions.
2. Open the file with a plain-text editor, such as Notepad on Windows. It must be the domain association file downloaded from your payment provider. If it contains a login page, an error message, or an unexpected JSON response, download it again from the provider or ask the provider for the correct file.
3. For a verification-text download with the wrong extension, make a copy and replace the final .json with .txt: for example, apple-developer-merchantid-domain-association.json becomes apple-developer-merchantid-domain-association.txt. Renaming preserves the contents. Do not leave .json at the end or edit, reformat, or convert the verification text.
4. Select the .txt copy in KORONA Event and select Save file. Then return to Lynck to finish domain registration.

Renaming an error response does not turn it into a verification file. If you are unsure which file you downloaded, ask your payment provider before uploading it. KORONA Event serves an uploaded file at the required address without a .txt or .json extension; you do not need to change that address.

Check device and browser expectations

Wallet buttons only render when the customer's environment supports them:

• Apple Pay requires an Apple device with a card set up in the wallet, and browser support is most reliable in Safari.
• Google Pay requires a supported browser with a payment method saved in the customer's Google account.

Ask the customer which device and browser they used before treating a missing button as a configuration problem.

Expected result

For Stripe, the affected domain shows an Active wallet status. For Lynck Apple Pay, the verification file is reachable and the domain is registered in the Lynck merchant area. For Lynck Google Pay in live mode, Google has approved the website integration, the live Google merchant ID is saved in KORONA Event, and Lynck has enabled Google Pay Express for the live account. Eligible customers then see the official wallet button in the cart. After wallet approval, the checkout displays the order review and any required information that is still missing.

Troubleshooting

Related articles

• Payment setup overview
• Check payment provider setup
• Troubleshoot Klarna and pay-by-link payment methods