Online Payments

Apple Pay

What is Apple Pay, and what has to be done before you can offer it as a payment method?

Edit "Apple Pay" on GitHub

Looking to streamline payments for your customers?

With Apple Pay, you can offer a fast, secure, and seamless checkout experience that customers love.

  • Speed: Transactions are completed with a single touch.
  • Security: Built-in encryption and biometric authentication (Face ID or Touch ID) ensure every payment is safe. Your customer’s card details are never shared.
  • Wide Reach: Apple Pay works online, in apps, and in stores, making it easier for customers to pay wherever they are.
  • Higher Conversions: Customers are more likely to complete purchases with quick, frictionless checkouts.
  • Active Users: 500 million active users worldwide.

Domain Verification

Seamless View integration only

Before we can enable Apple Pay for you, you need to complete a domain verification if you are using a Seamless View integration.

This is done to confirm that the website where you are using Apple Pay belongs to you. You need to verify all domains – both top-level and subdomains – where you plan on displaying the Apple Pay button and process payments. It is a security measure used to prevent fraud, ensure compliance and for merchant identification.

The domain verification is required for all Seamless View integrations, also Mobile SDK solutions.

It is not needed for native iOS SDK Apple Pay integrations, but you need to contact our integration team for assistance in the setup process.

No actions are necessary for Redirect integrations as it is on Swedbank Pay’s domain, making it our responsibility that the domain file is present and active.

You need a copy of our domain file.

  • Make sure you do not change, edit or manipulate the file in any way, shape or form.
  • The file should have NO EXTENSION, meaning there should not be any “.txt”, “.doc”, “.mp4” or any other extension to the file.

Upload the file to the following web path: https://[DOMAIN-NAME]/.well-known/apple-developer-merchantid-domain-association

  • Replace [DOMAIN-NAME] with your own domain.
  • If your website is https://www.example.com, then the site would be https://www.example.com/.well-known/apple-developer-merchantid-domain-association. Remember to use the fully qualified domain name (in this case www.example.com instead of example.com).
  • If you want to activate Apple Pay on multiple domains, for example https://ecom.payex.com and https://developer.swedbankpay.com, you need to upload the file to all of the unique domains.

If you’re presenting Seamless View payments in a custom plain web view implementation, you need to make sure that the provided baseURL in the call to loadHTMLString(_:baseURL:) is set to the same domain as where you host the file. If not, it may fail to validate, making it so payments with Apple Pay may not function.

For questions about uploading the file and making it available, please contact your domain administrator or provider for further instructions and assistance.

Verify that the file has been uploaded correctly by opening the site. You should see a series of letters and numbers.

  • You can compare it to our own verification file, found on this site.
  • If done correctly, they should look identical.
  • The verification file is a hex string that contains a JSON. If the file is modified or the file is saved in a different format, this may cause the validation to fail.

Once you have completed the steps above, please notify your integration contact to activate Apple Pay, and specify the domain on which you performed the configuration. If you don’t have a contact person, reach out to our support team.

If you’re using our iOS SDK, make sure that the webViewBaseURL is set to the same domain as where you host the file.

If you’re presenting Seamless View payments in a custom plain web view implementation in your iOS application, you need to make sure that the provided baseURL in the call to loadHTMLString(_:baseURL:) is set to the same domain as where you host the file. If not, it may fail to validate, making it so payments with Apple Pay may not function.

You also need to make sure that Apple Pay scripts are allowed to be loaded and executed in the web view (relevant if you’re implementing WKNavigationDelegate and your own webView(_:decidePolicyFor:decisionHandler:) implementation).

Apple Pay Terms And Conditions

Apple requires Swedbank Pay to identify whether and when you have accessed the Apple Pay Platform Web Merchant Terms and Conditions, and to record whether you have accepted and agreed to them.

We also need to require you to periodically incorporate updates or amendments to the terms of the Apple Pay Web Terms and Conditions, Apple Pay Web Guidelines, Apple Pay HI Guidelines, Apple Pay Best Practices Guide, or Apple Marketing Guidelines.

Unless you have already accepted as part of signing your agreement with Swedbank Pay, we can provide the following links for digital signature in Sweden and Norway.

If you are unable to sign the Apple Pay Web Terms and Conditions in Swedish or Norwegian digitally, please use the supplementary agreement template (click to download) in English, and e-mail it to agreement@swedbankpay.com together with Name, Organizational and Customer number. Your acceptance is needed before we can activate Apple Pay for you.