Skip to content

Choose which cookies you allow. You can change your mind at any time with “Cookie settings” in the footer. Cookie policy

EN – current language PT – Português
Request a quote
Get a quote

Payment integrations

Apple Pay and Google Pay on your website

We switch on Apple Pay and Google Pay in your online store, booking system or platform, through Stripe, Adyen or Mollie. Customers pay with the card already saved on their phone and approve with their face, fingerprint or passcode. With fewer fields to fill in on a phone, the last step of the purchase gets much shorter.

Why it is worth it

According to Wmtips, Apple Pay appears on 39% of websites that use a payment service. On a phone, typing sixteen digits, an expiry date and an address is the most tedious step of any purchase. With Apple Pay or Google Pay, customers see the total, approve with a glance or a fingertip, and the order is paid.

In an online store, the button can sit right on the product page for people who already know what they want. In a booking system, someone booking a table or a session on the way pays the deposit without reaching for their wallet.

Through which provider

Apple Pay and Google Pay are not separate providers: they run on top of the business's payment account. We work with Stripe, Adyen and Mollie. If you already use one of them, switching the wallets on is mostly configuration and testing. If you have no provider yet, we pick the one that best combines the wallets with Portuguese methods such as MB WAY and Multibanco.

Tested where customers buy

The buttons only appear when the customer's device, browser and wallet allow it, so we test on real iOS and Android phones. We check that the total, shipping and discounts show correctly in the wallet sheet, and that the order is recorded as paid on the website side.

Payment methods

  • Apple Pay
  • Google Pay
  • Card

Typical uses

  • Online stores where most visits come from phones
  • Last-minute bookings made on the move
  • Quick purchase straight from the product page
  • Subscriptions and renewals without retyping a card

What we set up

  • Both wallets switched on in the payment provider's account
  • The domain verification Apple Pay requires
  • Buttons on the product page, in the basket and at checkout, where they make sense
  • Address and contact details filled from the wallet when the store ships orders
  • Every payment confirmed through webhooks
  • Testing on real iPhones and Android phones, not just simulators

Payment providers

  • Stripe
  • Adyen
  • Mollie

Frequently asked questions

Do I need a contract with Apple or Google?

As a rule, no. Both wallets are switched on through your payment provider, in the same account that takes card payments. On the website side, we handle the domain verification Apple Pay asks for and where the buttons go.

Does every customer see the buttons?

No. Apple Pay shows on supported Apple devices and browsers, and Google Pay mainly on Android and Chrome, when the customer has a saved card. Everyone else sees the other methods, such as card, MB WAY or Multibanco.

Do Apple Pay and Google Pay have their own fees?

The payment is processed as a card payment, so your provider's card fees apply. We explain them in the proposal. Our own work is on request, quoted for each project. Request a quote

Is it safe for customers and for the business?

Yes. The card number is never shared with the website, which only receives a single-use token. The customer approves with biometrics or the phone's passcode, which already meets the strong authentication European banks require.

Shall we talk about your project?

Tell us what you have in mind and what you want to achieve.