We want to assure you that payments processed through ChargeAutomation using Apple Pay and Google Pay are treated as highly secure and authenticated transactions.
You can be confident that these payments meet or often exceed the necessary authentication requirements, minimizing risk for your business.
How Authentication Works for Mobile Wallets
Unlike standard card entry, transactions made using Apple Pay and Google Pay rely on the device itself to verify the cardholder's identity. This process is inherently strong and is the core reason these payments are considered highly secure:
Device-Level Authentication: Before a payment is finalized, the guest must authenticate the transaction using a secure method like Face ID, Touch ID, or a device passcode.
Issuer Acceptance: This device-level verification often satisfies the security requirements set by the card issuer, meaning they trust the transaction is legitimate because the physical device was unlocked and authorized by the cardholder.
The Role of 3D Secure (3DS)
For standard card payments, 3D Secure (3DS) adds an extra verification step (like a one-time code or bank login). For mobile wallets, this requirement is managed seamlessly in the background:
Automatic Triggering: If the guest's underlying credit card supports 3DS and the card issuer specifically requires it (even after device authentication), we will automatically trigger the 3DS process as part of the Apple Pay or Google Pay payment flow.
Key Takeaway for Property Managers
When a guest pays using Apple Pay or Google Pay, you can rely on the fact that the transaction has been securely authenticated via a combination of device verification and, where required, automatic 3D Secure protocols. This guarantees you are accepting payments from verified cardholders.