Google Pay

Google Pay is useful when a customer already has a card saved with Google and wants to avoid retyping it at checkout. The payment sheet can also collect a shipping address. Your website receives a payment token, passes it to its backend and sends it to the payment processor to complete the purchase.

Add it to an existing checkout

Begin with the supported processor list: a gateway integration uses your provider's Google Pay setup. Handling card data directly requires a separately assessed payment-card security environment. Some hosted checkout providers onboard their merchants themselves.

For your own web integration, complete the tutorial and integration checklist, then create a Business Profile in the Google Pay & Wallet Console. Select Merchant as the business type. Under Google Pay API > Integrations, choose Add website, enter the domain and select Gateway or Direct. Upload checkout screenshots and submit the website for approval. Once approved, the production code needs the merchant ID and the production environment setting.

Costs and availability

Google charges no additional fee for using the payment API. Your processor still handles the funds and charges its normal processing fees. Google Pay therefore adds a wallet option without replacing your merchant processing agreement.

Slovenia is on Google's list for payments on participating websites and apps. Contactless store payments use Google Wallet, with their own supported banks and devices. The in-app Google Pay API covers physical products and services; Android digital purchases covered by Google Play billing rules use that billing system.

Google says qualifying Visa and Mastercard device-token transactions can shift fraud chargeback liability to the issuer. This is conditional protection, so keep your existing fraud checks and confirm the applicable arrangement with your processor.