eWallet accounts store the merchant configuration needed for the Payments Library to display payment options and process transactions. Each eWallet account defines settings for a specific payment method type.
This guide covers eWallet account configuration in detail. For a quick setup to get started, see the Quickstart. What is an eWallet Account?
An eWallet account connects your Orchestra integration to specific payment methods through the Payments Library. When you create a session with the Payments Library, you specify which eWallet accounts to use, and the library displays the corresponding payment options to your customers.
eWallet Account Types
| Type | Description | Requirements |
|---|
| CardPay | Credit and debit card payments | PSP account configured in Orchestra |
| GooglePay | Google Pay digital wallet | Google merchant account, PSP with 3DS |
| ApplePay | Apple Pay digital wallet | Apple merchant account, domain verification, PSP with 3DS |
| PayPal | PayPal payments | PayPal Business account |
| BankPay | Bank transfers (Open Banking) | Everifin account, recipient bank details |
| UPI | Unified Payments Interface (India) | UPI merchant credentials |
Creating an eWallet Account
- Go to Resources > eWallet Accounts > Add Account in the Orchestra Portal
- Enter a Name for the account (e.g., “card-payments”, “google-pay-prod”)
- Select the eWallet Type for the payment method
- Configure the type-specific settings (see below)
- Click Save
CardPay Configuration
CardPay accounts enable credit and debit card collection through the Payments Library.
| Field | Description | Required |
|---|
| Merchant Identifier | Unique identifier for your merchant account, typically in reverse domain format (e.g., com.yourcompany.payments) | Yes |
| Merchant Display Name | Business name shown to customers on the payment form | Yes |
| Display Issue Number? | Show the card issue number field (used by some UK debit cards) | No |
| Display Owner Id? | Show a cardholder ID field for markets that require it | No |
| Perform 3Ds? | Enable 3D Secure authentication for card transactions. When enabled, requires 3DS-related fields below | No |
| Merchant Requestor Id Suffix | Suffix appended to the 3DS Merchant Requestor ID. Required when Perform 3Ds is enabled | Conditional |
| Merchant Url | Your website URL, sent to the 3DS server. Required when Perform 3Ds is enabled | Conditional |
BIN Routing Table
CardPay accounts support optional BIN-based routing. This table lets you route transactions to different Merchant IDs based on card BIN, brand, or MCC.
| Column | Description |
|---|
| Bin | Card BIN prefix to match (e.g., 411111 for test Visa cards) |
| Brand | Card brand (Visa, Mastercard, Amex, etc.) |
| MCC | Merchant Category Code for this routing rule |
| Merchant Id | The Merchant ID to use when this rule matches |
GooglePay Configuration
GooglePay accounts enable Google Pay wallet payments through the Payments Library.
| Field | Description | Required |
|---|
| Merchant Identifier | Your Google Pay Merchant ID from the Google Pay Business Console | Yes |
| Merchant Display Name | Business name shown in the Google Pay payment sheet | Yes |
Before creating a GooglePay eWallet account, you must register as a Google Pay merchant and complete Google’s integration requirements. See Google Pay Setup for details. ApplePay Configuration
ApplePay accounts enable Apple Pay wallet payments through the Payments Library. Apple Pay requires certificates for both merchant validation and payment decryption.
| Field | Description | Required |
|---|
| Merchant Identifier | Your Apple Merchant ID from the Apple Developer Portal (e.g., merchant.com.yourcompany) | Yes |
| Merchant Display Name | Business name shown in the Apple Pay payment sheet | Yes |
| Domain Name | The domain where Apple Pay will be used. Must be verified in the Apple Developer Portal | Yes |
| Client Certificate Pem | Merchant Identity Certificate in PEM format. Used for merchant validation during Apple Pay sessions | Yes |
| Client Certificate Private Key Pem | Private key for the Merchant Identity Certificate in PEM format | Yes |
| Payment Certificate Private Key Pem | Private key for the Payment Processing Certificate in PEM format. Used to decrypt payment tokens | Yes |
| Payment Certificate Pem | Payment Processing Certificate in PEM format | Yes |
Apple Pay setup requires creating certificates in the Apple Developer Portal and verifying your domain. See Apple Pay Setup for step-by-step instructions. PayPal Configuration
PayPal accounts enable PayPal payments through the Payments Library.
| Field | Description | Required |
|---|
| Merchant Identifier | Your PayPal Client ID from the PayPal Developer Dashboard | Yes |
| Secret | Your PayPal Client Secret from the PayPal Developer Dashboard | Yes |
You need a PayPal Business account to accept payments. See PayPal Setup for details on obtaining your API credentials. BankPay Configuration
BankPay accounts enable Open Banking payments through the Payments Library, allowing customers to pay directly from their bank account.
| Field | Description | Required |
|---|
| Merchant Identifier | Unique identifier for your merchant account | Yes |
| Merchant Display Name | Business name shown to customers during bank selection | Yes |
| Recipient Bank Iban | Your business bank account IBAN where funds will be deposited | Yes |
| Recipient Bank Bic | BIC/SWIFT code for your recipient bank account | Yes |
| Everifin Client Id | Client ID from your Everifin account (Open Banking provider) | Yes |
| Everifin Client Secret | Client Secret from your Everifin account | Yes |
BankPay uses Everifin as the Open Banking provider. Contact Orchestra support to set up an Everifin account for your integration.
UPI Configuration
UPI accounts enable Unified Payments Interface payments for customers in India.
| Field | Description | Required |
|---|
| Merchant Identifier | Your UPI Merchant ID or Virtual Payment Address (VPA) | Yes |
| Salt | Cryptographic salt used for secure transaction signing | Yes |
UPI is available for merchants operating in India. Contact Orchestra support for UPI integration requirements.
Using eWallet Accounts
When creating a Payments Library session, specify which eWallet accounts to enable:
curl --location 'https://api.orchestrasolutions.com/EWalletOperations' \
--header 'X-Api-Key: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"operation": "CHARGE",
"PaymentGatewayAccountId": "your-psp-account",
"AllowedeWalletAccountIds": ["card-payments", "google-pay-prod", "paypal-prod"],
"mode": "LIVE",
"CurrencyCode": "USD",
"Amount": "25.00"
}'
Next Steps
