> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slm.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.
# JusPay Configuration
| Payment Provider | Geographies | Currencies | Payment Methods | Retain Support | Automatic Chargeback Feed | Account Updater | API Version | Microservice? |
| - | - | - | - | - | - | - | - | - |
| JusPay Payment Aggregator | India | INR | \*\*Credit/Debit Cards -\*\**Yes* **SEPA DD**- *No* **Tokenized Credit Card**- *Yes* **Hosted Pages** - *No* **Alternative Payments** - *PayU, *Razorpay*, Checkout.com* **Digital Wallets** - *PayTM, Amazon pay, mobikwik, phonepe, PayPal* | **Tokenized Credit Card** - *Yes* **Detokenize PAN** - *No* **Detokenize BIN**- *No* **Partial Auth** - *No* **Forced Deposit** - *No* | No | No | 2018-10-25 | No |
## Required Merchant Information
\[
]\(../images/JusPay.xlsx)
| Name | Expected Value | Value | Description |
| - | - | - | - |
| JusPay: api\_key | API key for merchant, generated at processor | | |
| For Checkout.com | Secret Key Public Key Webhook Auth Key (optional) | | These are the keys generated by Checkout.com (at the Checkout.com portal), and the need to be added on the Juspay Dashboard while configuring the Gateway. We have to select the correct gateway ,either 2.0 or 2.1, based on the API used by merchant to generate the Token. |
| Does provider need to whitelist IPs | No | | |
| Does a merchant need to grant access to Vindicia | No | | |
| Chargeback feed | No | | |
| Account Updater | No | | |
## Desired Merchant Configuration
(No optional merchant config for JusPay)
| Name | Value | Comments |
| - | - | - |
| N/A | N/A | |
* **[JusPay Merchant Setup Instructions](../topics/jusPayConfiguration_r#)**
* **[JusPay Detailed Information on Integration](../topics/jusPayConfiguration_r#)**
**Parent topic:**[Payment Provider Specific Configuration](../topics/PaymentProvidersSpecificConfiguration)
## JusPay Merchant Setup Instructions
The following Instructions are written for Vindicia CTS and services delivery staff.
To configure a merchant to use JusPay payment processor:
### Merchant Payment Providers
1. In Subscribe Portal 1.0, using you’re admin account, go to **Admin** > **Merchant Configurations**.
2. Select the relevant **Merchant** from the drop-down list.
3. Click **Edit Merchant Configurations**.
4. Enter the **Jira Ticket #** for configuring your merchant payment setup.
5. Add JusPay to **Merchant Payment Providers**:
| Payment Provider Name | Account Number | PP Type | Active |
| - | - | - | - |
| JusPay (1068) | \ | BRD(1) | 1 |
1. Select **JusPay (1068)** as the payment provider and click **ADD**.
2. Leave **Account Number** blank.
3. Set **PP Type** as **BRD**.
4. Set **Active** to **1**.
### Routing Rule
1. Add a **Routing Rule** for JusPay.
| Ordinal | Payment Provider | Value | Rule Method | Active |
| - | - | - | - | - |
| 1 | JusPay (1068) | | default\_method(1) | 1 |
1. Select **JusPay (1068)** as the payment provider and click **ADD**.
2. Add an **Ordinal** value of **1**.
3. Leave **Value** blank.
4. Add a **Rule Method** value of **default\_method(1)**.
5. Set **Active** to **1**.
**Note:** If the test payment provider is configured, set its **Active** value to **0**.
**Note:** If a merchant account is set up with several payment providers, the payment provider with highest **Ordinal** value has priority. If routing will be shared amongst payment providers, see [Configuration Method - Payment Providers Routing Rules](routingRulesAbout) for examples of possible configurations.
### Name/Value Pairs
The below api\_key value is for Vindicia internal testing and should not be shared with merchants.
| Name | Value |
| - | - |
| JusPay: api\_key | D890C4508AB418C9E10BF560C59E84 |
| JusPay:response\_key | C092D61ED854962B02EDC76ECBCF99 |
| JusPay:merchant\_id | vindicia (Configured at Juspay end) |
| JusPay:client\_id | vindicia (Configured at Juspay end) |
| JusPay:enable\_gateway | CHECKOUT (Backend gateway name to whom gateway can forward the payment request) |
| JusPay:gateway\_reference\_id | Retain\_XXXXX (name of the Gateway configured at the Juspay Dashboard) |
### Configuring the Checkout.com Gateway
To use Checkout.com as a gateway with JusPay, complete the following steps in the JusPay portal.
1. Create a new merchant instance in the JusPay portal.
2. Click **Create Gateway**.
3. Add a **Gateway Type** of **Checkout**.
4. Add the merchant's public and secret keys from their Checkout.com merchant instance.
5. Add the **Webhook Auth Key**, if the merchant has it configured for Checkout.com.
6. Select the **Cards** checkboxes based on the merchant’s requirements.
7. select the **Supported Currencies** checkboxes based on merchant’s requirements.
### Creating the Secret and Public Keys from the Checkout.com Portal
Checkout.com supports two versions of the API (2.0 and 2.1). The API version that the merchant uses to create the **Token** is the same version we need to configure in the Juspay dashboard.
We have two separate dashboards to generate the keys for 2.0 and 2.1:
* Version 2.0: [https://sandbox.checkout.com/](https://sandbox.checkout.com/)
* Version 2.1: [https://identity-sandbox.checkout.com/](https://identity-sandbox.checkout.com/)
**Important:** When generating keys, you must toggle off the **Allow any processing channel** option on the **Developers** > **Keys** > **Create New Keys** screen.
**Parent topic:**[JusPay Configuration](../topics/jusPayConfiguration_r#)
## JusPay Detailed Information on Integration
Vindicia supports the following Payment Operations for JusPay and in the following geographical areas:
| Payment Operation | Yes/No | Notes |
| - | - | - |
| **Standard Implementation Features** | | |
| Verification (no Auth) | Yes | |
| Minimal Authorization (\$0) policies, by card type) | No | |
| AVS check with standard result mapping | No | |
| CVV/CVN check with standard result mapping | Yes | |
| Support real-time authorization (stand-alone Auth) | Yes | |
| Void | No | |
| Conditional deposit (auth and capture combination) | Yes | |
| Capture (stand-alone capture) | Yes | |
| One-time transactions (real-time) | Yes | |
| Recurring transactions (flagged recurring) | Yes | |
| Refunds - Full | Yes | |
| Refunds - Partial | Yes | |
| 3DS | No | |
| CITMIT/Card On File | No | JusPay uses mandates to manage recurring billing |
| Map error/response/result codes to standard actions (Success/Decline/Reject) | Yes | |
| **Special Implementation Features** | | |
| Implemented via Payments Microservice | No | |
| Retrieve and store paymentProcessorTransactionId | Yes | |
| Retrieve and store Extended Card/Auth Attributes | No | |
| Support tokenization (for Retain) | Yes | |
| Support BIN/Last-4/Expiry Retrieval from external Token | No | |
| Support detokenization (Subscribe retrieves full PAN/CC details | No | |
| Support Card Type identification (from BIN or API) | No | |
| Support Visa/general "Stored Credential" flags | Partial | Supported for Checkout.com gateway |
| Account Updater/Amex Card refresher | No | |
| Automated/manual chargeback feed | No | |
| **Retain Support** | | |
| Support token as payment method | Yes | |
| Support detokenization to full PAN | No | |
| Support detokenization to get BIN | No | |
| Support Partial Authorization | No | |
| Support Balance Retrieval | No | |
| Support Forced Deposit | No | |
### Payment Processor Documentation
Links to docs:
* [https://developer.juspay.in/docs](https://developer.juspay.in/docs)
* [https://developer.juspay.in/docs/resources](https://developer.juspay.in/docs/resources)
### Error Codes
[https://www.checkout.com/docs/resources/codes/response-codes#Overview](https://www.checkout.com/docs/resources/codes/response-codes#Overview)
**Parent topic:**[JusPay Configuration](../topics/jusPayConfiguration_r#)
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.