Payments Library

The Payments Library (@pcibooking/ewallet) is a client-side JavaScript library that renders a card form and payment buttons in your checkout page. The cardholder enters their card details or selects a digital wallet, and the library tokenizes the card through PCI Booking. Card data never touches your servers.

How It Works

Your server creates a payment session with PCI Booking, specifying the operation type (e.g. TOKENIZE).
Your page initializes the library with the session token.
The library renders the card form and available payment buttons.
The cardholder enters their card or selects a payment method.
The library sends the card data directly to PCI Booking, which tokenizes it and returns a token to the library.
Your page receives the token via callback and sends it to your server.

const engine = new eWallet.Engine(sessionToken);
const methods = await engine.checkAvailability();

engine.payBy(methods, function(result) {
  if (!result) return;

  const [data, success] = engine.parseResultToken(result.token);
  if (data.clientSuccess && success) {
    // Send result.token to your server
  }
}, {
  containerSelector: '#payment-buttons'
});

Tokenization-Capable Methods

The following payment methods support tokenization through the library:

Method	What Happens
CardPay	Cardholder enters card details in a form rendered by the library. Card is tokenized and stored in PCI Booking.
Apple Pay	Cardholder authorizes via Face ID / Touch ID. The Apple Pay token is tokenized and stored in PCI Booking.
Google Pay	Cardholder selects a card from their Google account. The Google Pay token is tokenized and stored in PCI Booking.

Other methods (PayPal, BankPay, UPI) process charges directly without tokenization. See Supported Payment Methods for the full list.

3D Secure

3DS is handled automatically based on the payment method:

CardPay. When enabled, a 3DS challenge is presented to the cardholder if required by the issuing bank. The cardholder has 5 minutes to complete the challenge. If the challenge times out, the payment is cancelled and the callback receives undefined. See 3DS Merchant Setup to configure your merchant details for the challenge screen.
Apple Pay and Google Pay. 3DS authentication is handled natively by the wallet provider. No additional configuration needed.
PayPal, BankPay, UPI. 3DS does not apply. Each provider handles authentication through its own flow.

For tokenization operations (TOKENIZE, CHARGE_AND_TOKENIZE, PREAUTH_AND_TOKENIZE), the result token includes 3DS authentication data that can be stored with the token for subsequent transactions. See 3DS Auth Management for details.

Next Steps