Skip to main content

​
Payment Methods Overview

​
CardPay

Credit and debit card payments with full 3D Secure support. Works in all modern browsers. The card form is rendered by the Payments Library in either popup or iframe mode, ensuring card data never touches your servers. Browser support: All modern browsers (Chrome, Firefox, Safari, Edge) Operations: CHARGE, TOKENIZE, CHARGE_AND_TOKENIZE, PREAUTH_AND_TOKENIZE, GATEWAY_TOKENIZE

​
Stored Cards (Returning Customers)

CardPay can offer returning customers their previously tokenized cards. Pass up to 3 stored cards in the session creation request; the card form then shows a Pay by {brand} ****{last 4} button per card alongside the option to enter another card. When the payer selects a stored card, they enter only the CVV; the charge runs against the real card resolved from the token.
  • The display details (brand, last 4, name, expiration) are supplied by you and shown to the payer as-is. Keep them in your own system, or fetch them just before the session with Retrieve Token Metadata or Query Tokens.
  • Stored cards cannot be used with the TOKENIZE operation, and a payment made with a stored card in a CHARGE_AND_TOKENIZE or PREAUTH_AND_TOKENIZE session is not tokenized again.
  • When the payment gateway runs its own authentication on a page of its own, a payer paying with a stored card is sent to that page after entering the CVV. Gateways whose authentication is a one-time code form or HTML supplied by the gateway cannot be used with stored cards; offer the new card form for those.

​
Apple Pay

Native Apple Pay integration for Safari on iOS and macOS. Requires Apple Pay merchant setup through PCI Booking. Browser support: Safari on iOS 10+ and macOS Sierra+ Device support: iPhone, iPad, Mac with Touch ID or Apple Watch
Apple Pay buttons only appear when checkAvailability() detects a compatible device and browser.
Operations: CHARGE, TOKENIZE, CHARGE_AND_TOKENIZE, PREAUTH_AND_TOKENIZE, GATEWAY_TOKENIZE

​
Google Pay

Native Google Pay integration for Chrome and Android. Requires Google Pay merchant setup through PCI Booking. Browser support: Chrome on Android, desktop Chrome with linked Google account Device support: Android devices, desktop with Chrome Operations: CHARGE, TOKENIZE, CHARGE_AND_TOKENIZE, PREAUTH_AND_TOKENIZE, GATEWAY_TOKENIZE

​
How Wallet Payments Are Processed

When a payer pays with Apple Pay or Google Pay, PCI Booking decrypts the wallet payment, takes the card details from it, and stores them as an ordinary token. Your payment provider then receives the payment as a card transaction, with the wallet’s authentication data attached as 3D Secure data where it is available. A few integrations pass the payment on as a wallet payment instead. What the token contains:
  • Apple Pay: card number, expiry date, cardholder name, and the authentication data (ECI and cryptogram).
  • Google Pay: card number and expiry date. The authentication data is included only when Google Pay returns a cryptogram. A Google Pay payment made with a card saved to the Google account (not a device token) has no cryptogram and no cardholder name.
  • No security code in either case. If your payment provider account is set to require a security code on every charge, it declines wallet payments. Ask your provider whether it can relax that rule for wallet payments.

​
PayPal

PayPal checkout integration. Supports charge operations only, the user is redirected to PayPal to authorize the payment. Browser support: All modern browsers Operations: CHARGE only

​
BankPay

Open Banking and ACH direct bank payments. The user selects their bank and authorizes the payment through their banking app or website. Browser support: All modern browsers Operations: CHARGE only Availability: Varies by region and bank support

​
UPI

Unified Payments Interface for instant payments in India. The user scans a QR code or enters their UPI ID to complete the payment. Browser support: All modern browsers Operations: CHARGE only Availability: India only
For credential setup instructions for each payment method, contact your PCI Booking account manager or refer to the Payments Library Credentials.

​
Next Steps

Payments Library Overview

Architecture, capabilities, and how the library fits into your integration.

Setup Guide

Install the library, create a session, and run your first payment.

Library Reference

Full API surface: constructor parameters, methods, callbacks, and operation types.