Skip to main content
This page is part of the Payments Library Guides. Prefer direct API calls instead? See REST API Guides.
Prerequisites: API key, Payment Gateway Account, and eWallet Account configured. The Orchestra Payments Library displays payment buttons and handles the payment UI. It supports card entry, Apple Pay, Google Pay, PayPal, bank payments, and UPI.
Available on npm as @orchestrasolutions/ewallet.

Installation

Data Flow

Payments Library Data Flow Your server creates a session with Orchestra and passes the JWT to the client. The client initializes the library, displays payment buttons, and handles customer interaction. After payment, the result JWT is returned to the client, which passes it to your server for validation with Orchestra.

Quick Start

1. Initialize the Engine

The sessionToken comes from your backend via POST /EWalletOperations. Here is how to create a session on your server:

2. Check Available Payment Methods

3. Display Buttons

Add container elements to your HTML:
Each payment method requires its own container element with a unique selector. If you add multiple payment methods, create a separate container for each.
Render buttons for available methods:

4. Handle Results

Your backend should validate the result token using POST /EWalletOperations/validateResults before fulfilling orders.

Payment Methods

What’s Next

Supported Payment Methods

CardPay, ApplePay, GooglePay, PayPal, BankPay, UPI

Library Reference

Button styling, result parsing, address collection, localization

Result Handling

Parse and validate payment results

Complete Example

End-to-end integration example