Google Pay™ in apps: We do not currently support launching Google Pay™ within an in-app solution. If you want to implement Google Pay™ in your web-view application, you will need to open it in a browser and open the Checkout from there.
Pay Smarter with Google Pay™!
- Fast Transactions: Tap, click, or swipe—pay in seconds.
- Secure Payments: Advanced encryption keeps your card details safe.
- Seamless Convenience: Save cards, loyalty programs and tickets all in one place.
- Widely Accepted: Use it anywhere Google Pay is supported..
Merchant ID
You need to sign up for a Google Developer Account and create a business profile and payment profile.
After creating the business profile, you will be able to see your Merchant ID in the top right corner of the page. We need that ID in order to activate Google Pay for you.
Be sure to register your domain/package and submit screenshots of your integration for approval. Login to Google Pay™ & Wallet Console, go to the Google Pay™ API tab to upload and submit the screenshots. You should provide visuals for 5 steps of the purchase flow (e.g. add to cart, checkout, payment and confirmation - where the confirmation screenshot can be used for both screenshot 4 and 5).
We have provided pre-approved integration screenshots to ease this part of the process. The images in the ZIP file are named with the corresponding purchase steps where they should be uploaded.
If you are using the Redirect implementation, you need to register ecom.payex.com, and not your own page, as the domain. This is because the payment is generated from Swedbank Pay, and Google Pay needs to recognize that as the authorized origin of the request.
Your Merchant ID will only work in production environment once Google complete their review and approve your submitted integration. Unless you have provided us with your Merchant ID as part of signing your agreement with Swedbank Pay, you can e-mail us it at agreement@swedbankpay.com together with Name, Organizational and Customer number.
Implementation Paths
No additional steps are required. Contact Customer Operations after signing up with Google, and give them your Merchant ID to setup your contract. Once set up, the option to pay with Google Pay™ should appear in your implementation as long as the end user’s device supports it.
Please remember that you must adhere to the Google Pay™ API’s Acceptable Use Policy and accept the terms defined in the Google Pay™ API’s Terms of Service .
No additional steps are required. Contact Customer Operations after signing up with Google, and give them your Merchant ID to setup your contract. Once set up, the option to pay with Google Pay™ should appear in your implementation as long as the end user’s device supports it.
Please remember that you must adhere to the Google Pay™ API’s Acceptable Use Policy and accept the terms defined in the Google Pay™ API’s Terms of Service .
Implementation Details
3DS is enabled by default. You will not handle any payment details or sensitive data at all during the purchase process. The data is encrypted and sent to our PCI zone, where we decrypt and handle processing of the cards. You can’t selectively enable/disable what types of authorization methods you receive. We handle all kinds on our end.
Swedbank Pay will handle both gateway and gatewayMerchantID internally during the onboarding, and it is not an issue you need to address. Please note that Merchant ID and gatewayMerchantID is not the same. The Merchant ID is given to you in the Google Console. The gatewayMerchantID is the ID given to a you from the gateway.
We accept both PAN_ONLY and CRYPTOGRAM_3DS cards in all countries
where Google Pay is supported.
Any merchant onboarded with Swedbank Pay who’s been given access to Google Pay™ can request the payer to provide a billing address in relation to shipping them physical goods. These details are encrypted and can only be accessed by the merchant that requested the billing details and are deleted after 30 days.
You will not handle any of the customers’ payment details. The encrypted details are passed on to our backend systems, which in turn pass them to our internal PCI environment for processing. Within the PCI environment, a tokenized representation of the card is created, which is then used outside of the PCI environment to ensure the customers details are kept safe.