Personal Workspace

Getting Started

Authentication

Base URL

PayOut

IMPS Send Payout Request

UPI Send Payout Request

Get Payout Status

Get Balance

Callback Response

Invoice Payin

Create Transaction

Get Transaction Status

The S2S PayIN section of the EFIPAY Payment API allows users to securely process card payments and retrieve detailed information about card transactions. With this API section, users can seamlessly integrate card payment functionality into their applications, ensuring a smooth and secure payment experience for their customers.

S2S PayIn Manual

Get Payment Method

Update Transaction

S2S PayIn Automatic

Payin Mobile UPI Intent

EFIPAY - Payment API's

EFIPAY - API Documentation

Production

Sandbox

<p class="slate-p" placeholder="Type / for widgets">Welcome to EFIPAY API Doc!</p><p class="slate-p" placeholder="Type / for widgets">
The EFIPAY payment solution designed to streamline transactions in the modern economy. With EFIPAY, users can enjoy a seamless and secure payment experience.</p><p class="slate-p" placeholder="Type / for widgets"></p><h1 class="slate-h1">How to get keys</h1><p class="slate-p" placeholder="Type / for widgets">Our API integration starts in your dashboard. Browse to the account settings section and get your first API Key and Salt Key.</p><p class="slate-p" placeholder="Type / for widgets"></p><div style="text-align:left"><img src="https://theneo-prod-public.s3.us-east-1.amazonaws.com/images-1706863093874.jpg" alt="" style="width:50%"/></div><p class="slate-p" placeholder="Type / for widgets"></p><h3 class="slate-h3"> Security Measures:  </h3><p class="slate-p" placeholder="Type / for widgets">  Following these steps fortifies your API against potential threats, ensuring the integrity and confidentiality of your data.</p><ul class="slate-ul"><li class="slate-li"><div style="position:relative">Safeguard your keys: Keep API keys and salt keys confidential to prevent unauthorized access.</div></li><li class="slate-li"><div style="position:relative">Ensure HTTPS Usage: Encrypt data transmission using HTTPS to prevent eavesdropping and tampering.</div></li></ul><p class="slate-p" placeholder="Type / for widgets"></p>


The EFIPAY payment solution designed to streamline transactions in the modern economy. With EFIPAY, users can enjoy a seamless and secure payment experience.

Our API integration starts in your dashboard. Browse to the account settings section and get your first API Key and Salt Key.

  Following these steps fortifies your API against potential threats, ensuring the integrity and confidentiality of your data.

 algorithm to authenticate your requests. The idea is simple, every request (URL path + body) needs to be signed using your API Secret. Then our server makes sure the signature is correct and processes the query. 

This  provides a comprehensive guide on encrypting and signing API requests using JavaScript. It utilizes the CryptoJS library to implement HMAC-SHA256 encryption for securing the requests.

All private REST requests must contain the following headers:

1. Encryption and Signing Function:

This function takes four parameters:

It returns a string representing the generated signature for the API request.

You can use this function to sign your API requests before sending them to ensure their authenticity and integrity.

 function that you can use to generate a signature for your API request. To get started, ensure that CryptoJS is installed in your project. You can install it via npm using the following command:

> with your actual API key and salt key, respectively. After executing this code, you will obtain the generated signature for your API request.

4. How to Include Signing Keys in API Headers:

After generating the necessary keys, you can include them in your API headers to authenticate and authorize your requests. Below is an example of how to include the generated keys in your API headers using JavaScript:

 with the actual URL of your API endpoint. This code snippet demonstrates how to send an authenticated API request using the Fetch API in JavaScript.

<p class="slate-p" placeholder="Type / for widgets"></p><p class="slate-p" placeholder="Type / for widgets"><span style="background-color:rgb(255, 255, 255);color:rgb(13, 13, 13);font-size:16px" class="slate-color"><span style="background-color:rgb(255, 255, 255);color:rgb(13, 13, 13);font-size:16px" class="slate-backgroundColor">The base URL is the root address for all API calls. Depending on the stage of development or deployment, you will use either the production or sandbox base URL. Ensure you are using the correct base URL to avoid unintended effects, such as affecting live data when testing.</span></span></p><p class="slate-p" placeholder="Type / for widgets"><span style="background-color:rgb(255, 255, 255);color:rgb(13, 13, 13);font-size:16px" class="slate-color"><span style="background-color:rgb(255, 255, 255);color:rgb(13, 13, 13);font-size:16px" class="slate-backgroundColor"></span></span></p><h3 class="slate-h3">Production Environment</h3><p class="slate-p" placeholder="Type / for widgets">The production environment is meant for live applications. When your application is ready for deployment and intended for real users, use the production base URL for all API requests.</p><p class="slate-p" placeholder="Type / for widgets"></p><h3 class="slate-h3">Sandbox Environment</h3><p class="slate-p" placeholder="Type / for widgets">The sandbox environment is a testing environment that mirrors the production environment but does not affect live data. Use the sandbox base URL for testing, development, and experimentation to ensure that your application behaves as expected before deploying it to production.</p><p class="slate-p" placeholder="Type / for widgets"></p><h3 class="slate-h3">Choosing the Right Environment</h3><ul class="slate-ul"><li class="slate-li"><div style="position:relative">Use the <span style="color:var(--tw-prose-bold)" class="slate-color"><strong style="color:var(--tw-prose-bold)" class="slate-bold">production environment</strong></span> for all API calls related to your live application. This environment should be used with real transactions and when your application is being used by actual users.</div></li><li class="slate-li"><div style="position:relative">Use the <span style="color:var(--tw-prose-bold)" class="slate-color"><strong style="color:var(--tw-prose-bold)" class="slate-bold">sandbox environment</strong></span> for development, testing, and experimentation. This environment is ideal for trying out new features or making changes to your application without the risk of affecting your live data.</div></li></ul><h3 class="slate-h3">Notes and Best Practices</h3><ul class="slate-ul"><li class="slate-li"><div style="position:relative">Always ensure you are using the correct base URL for your intended environment to prevent data corruption or unintended side effects.</div></li><li class="slate-li"><div style="position:relative">Regularly test your application in the sandbox environment before any production deployment.</div></li><li class="slate-li"><div style="position:relative">Keep your API keys or authentication credentials separate for each environment to enhance security and prevent accidental access to the production environment.</div></li></ul><p class="slate-p" placeholder="Type / for widgets"></p>

The base URL is the root address for all API calls. Depending on the stage of development or deployment, you will use either the production or sandbox base URL. Ensure you are using the correct base URL to avoid unintended effects, such as affecting live data when testing.

The production environment is meant for live applications. When your application is ready for deployment and intended for real users, use the production base URL for all API requests.

The sandbox environment is a testing environment that mirrors the production environment but does not affect live data. Use the sandbox base URL for testing, development, and experimentation to ensure that your application behaves as expected before deploying it to production.

<p><span><span>The Payout API allows users to withdraw funds from their wallet using two methods: IMPS (Immediate Payment Service) and UPI (Unified Payments Interface). This document outlines the steps for initiating a payout, handling cal</span></span></p>

The Payout API allows users to withdraw funds from their wallet using two methods: IMPS (Immediate Payment Service) and UPI (Unified Payments Interface). This document outlines the steps for initiating a payout, handling callbacks for transaction outcomes, and checking transaction status.

To initiate a payout via IMPS, the user must provide their bank account details. The required information typically includes the account number, IFSC code, and the account holder's name.

For a UPI transaction, the user needs to provide their UPI ID. A UPI transaction is generally quicker and requires less information.

After a transaction is success/failed, a callback will be sent to a predefined URL with the transaction details. This callback contains information about the transaction's success or failure.

The Status API can be used to check the current status of a transaction. This is useful for verifying transactions when a callback has not been received.

To check the status of a transaction, the 

<p>With Invoice Payin, you can start invoice transactions using the payment interface from efipay. </p><p>Unlike S2S Payin, you don't have to handle designs. Simply use our payment page to collect payments from users.</p><p></p><ol><li><div><strong>Create Transaction: </strong></div></li></ol>

With Invoice Payin, you can start invoice transactions using the payment interface from efipay. 

Unlike S2S Payin, you don't have to handle designs. Simply use our payment page to collect payments from users.

<p>For customizing your payment page with your brand design, leverage the S2S Payin API to access payment details and effortlessly update transactions. S2S Payin provides convenient REST API access for payment processing. Follow the outlined steps below for comprehensive guidance on integration and customization.</p><p><strong>Follow the below steps to complete </strong></p>

For customizing your payment page with your brand design, leverage the S2S Payin API to access payment details and effortlessly update transactions. S2S Payin provides convenient REST API access for payment processing. Follow the outlined steps below for comprehensive guidance on integration and customization.

: Begin by creating a transaction using the API, ensuring all required parameters are filled, especially the accurate order_id, pivotal for retrieving payment information in the next step.

: Retrieve payment method details by passing the order_id, acquiring essential information like QR Code or UPI details. Proceed to transfer money via UPI using this provided information.

 After completing the UPI payment, proceed to update the transaction by entering the UTR number and attaching the payment reference file. Once submitted, the transaction will be verified using the provided UTR number.

Monitor the transaction status through the dedicated API, providing updates on the ongoing verification process and allowing you to stay informed about the current status.

<p class="slate-p" placeholder="Type / for widgets">For customizing your payment page with your brand design, leverage the S2S Payin API to access payment details and effortlessly update transactions. S2S Payin provides convenient REST API access for payment processing. Follow the outlined steps below for comprehensive guidance on integration and customization.</p><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">Follow the below steps to complete </strong></p><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">Step 1 - Create Transaction</strong>: Begin by creating a transaction using the API, ensuring all required parameters are filled, especially the accurate order_id.</p><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">Step 2 - Redirection</strong>: You will get a redirection URL in the response, which is used to redirect back to the payment page where user can pay for the transaction.</p><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">Step 3 - Get Transaction Status: </strong>Monitor the transaction status through the dedicated API, providing updates on the ongoing verification process and allowing you to stay informed about the current status.</p><p class="slate-p" placeholder="Type / for widgets"></p>

: Begin by creating a transaction using the API, ensuring all required parameters are filled, especially the accurate order_id.

: You will get a redirection URL in the response, which is used to redirect back to the payment page where user can pay for the transaction.

The reference name for the invoice (Min: 3, Max: 255)

name

The payment type for the transaction. Supported Inputs: inr

payment_type

The preferred inr payment type. Supported Inputs: UPI_INTENT

inr_type

The percentage of commission earned by the merchant for the transaction.

merchant_commission_percentage

The unique identifier for the order associated with the transaction.

order_id

amount

The URL to send callbacks or notifications to regarding the transaction.

callback_url

The URL to redirect the user to if the transaction is canceled.

cancel_url

The URL to redirect the user to after a successful transaction.

success_url

The URL to redirect the user to if the transaction fails.

failure_url

A description or note associated with the transaction.

description

email

phone

billing_city

billing_state

billing_country

billing_zipcode

primary_billing_address

secondary_billing_address

X-Api-Key

X-Api-Signature

success

message

code

data

error

error_code

The transaction has been initiated for payin. 

Initiated

User Paid

Success

Rejected

User cancelled the transaction before paying. 

Cancelled

Failed

<p class="slate-p" placeholder="Type / for widgets"><span style="background-color:rgb(255, 255, 255);color:rgb(13, 13, 13);font-size:16px" class="slate-color"><span style="background-color:rgb(255, 255, 255);color:rgb(13, 13, 13);font-size:16px" class="slate-backgroundColor">When certain API requests are made, a callback response may be sent to a specified URL to inform your application about the status or result of the request. This section details the structure, types, and handling of callback responses from our API.</span></span></p><h3 class="slate-h3">Configuring Callback URLs</h3><p class="slate-p" placeholder="Type / for widgets">Before you can receive callback responses, ensure you have set up and provided a callback URL in your API request. The callback have to be in POST method, so that you will receive the callback properly.</p><h3 class="slate-h3">Callback Response Structure</h3><p class="slate-p" placeholder="Type / for widgets">Callback responses typically contain a JSON payload with a standard structure. This structure may include, but is not limited to, the following fields:</p><p class="slate-p" placeholder="Type / for widgets"></p><h2 class="slate-h2">Handling Encrypted Callback Responses</h2><p class="slate-p" placeholder="Type / for widgets">If your callback responses are encrypted for enhanced security, you must decrypt them to access the actual data. This section outlines the decryption process based on the encryption method used by our API.</p><h3 class="slate-h3">Understanding Encrypted Callbacks</h3><p class="slate-p" placeholder="Type / for widgets">Encrypted callbacks ensure sensitive information is securely transmitted. Only parties with the correct decryption key can access the original data, protecting it from unauthorized access or eavesdropping.</p><h3 class="slate-h3">Encryption Method</h3><p class="slate-p" placeholder="Type / for widgets">Our API uses the following encryption method for callback responses:</p><ul class="slate-ul"><li class="slate-li"><div style="position:relative"><span style="color:var(--tw-prose-bold)" class="slate-color"><strong style="color:var(--tw-prose-bold)" class="slate-bold">Algorithm</strong></span>: (Specify the algorithm, e.g., AES-128)</div></li><li class="slate-li"><div style="position:relative"><span style="color:var(--tw-prose-bold)" class="slate-color"><strong style="color:var(--tw-prose-bold)" class="slate-bold">Mode</strong></span>: (Specify the mode, e.g., CBC)</div></li><li class="slate-li"><div style="position:relative"><span style="color:var(--tw-prose-bold)" class="slate-color"><strong style="color:var(--tw-prose-bold)" class="slate-bold">Salt Key</strong></span>: The decryption key is your Salt Key provided separately for security reasons. Ensure you store it securely and do not expose it in your application code or version control systems.</div></li></ul><h3 class="slate-h3">Decryption Process</h3><p class="slate-p" placeholder="Type / for widgets">Below is the JavaScript function that you can use to decrypt an encrypted callback response:</p><pre class="slate-CodeBlockElement slate-code_block"><div contenteditable="false"><div ><span aria-live="polite" aria-atomic="false" aria-relevant="additions text" ></span><div ><div ><div >Select...</div><div ><div  style="display:inline-block"><input type="text" autoCapitalize="none" autoComplete="off" autoCorrect="off" id="react-select-20-input" spellcheck="false" tabindex="0" value="" aria-autocomplete="list" style="box-sizing:content-box;width:1px;label:input;background:0;border:0;font-size:inherit;opacity:1;outline:0;padding:0;color:inherit"/><div style="position:absolute;top:0;left:0;visibility:hidden;height:0;overflow:scroll;white-space:pre"></div></div></div></div><div ><span ></span><div  aria-hidden="true"><svg height="20" width="20" viewBox="0 0 20 20" aria-hidden="true" focusable="false" ><path d="M4.516 7.548c0.436-0.446 1.043-0.481 1.576 0l3.908 3.747 3.908-3.747c0.533-0.481 1.141-0.446 1.574 0 0.436 0.445 0.408 1.197 0 1.615-0.406 0.418-4.695 4.502-4.695 4.502-0.217 0.223-0.502 0.335-0.787 0.335s-0.57-0.112-0.789-0.335c0 0-4.287-4.084-4.695-4.502s-0.436-1.17 0-1.615z"></path></svg></div></div></div></div></div><code class="language-javascript keep-markup drop-tokens"><div class="slate-code_line">async function decrypt(key, data) {</div><div class="slate-code_line">    try {</div><div class="slate-code_line">        const parts = data.split(&quot;:&quot;);</div><div class="slate-code_line">        const ivBytes = Uint8Array.from(atob(parts[1]), c =&gt; c.charCodeAt(0));</div><div class="slate-code_line">        const encryptedData = Uint8Array.from(atob(parts[0]), c =&gt; c.charCodeAt(0));</div><div class="slate-code_line"></div><div class="slate-code_line">        const algorithm = { name: &apos;AES-CBC&apos;, iv: ivBytes };</div><div class="slate-code_line">        const keyBytes = await crypto.subtle.importKey(</div><div class="slate-code_line">            &apos;raw&apos;,</div><div class="slate-code_line">            new TextEncoder().encode(key),</div><div class="slate-code_line">            &apos;AES-CBC&apos;,</div><div class="slate-code_line">            false,</div><div class="slate-code_line">            [&apos;decrypt&apos;]</div><div class="slate-code_line">        );</div><div class="slate-code_line"></div><div class="slate-code_line">        const decryptedData = await crypto.subtle.decrypt(</div><div class="slate-code_line">            algorithm,</div><div class="slate-code_line">            keyBytes,</div><div class="slate-code_line">            encryptedData</div><div class="slate-code_line">        );</div><div class="slate-code_line"></div><div class="slate-code_line">        return new TextDecoder().decode(decryptedData);</div><div class="slate-code_line">    } catch (ex) {</div><div class="slate-code_line">        console.error(ex);</div><div class="slate-code_line">        return null;</div><div class="slate-code_line">    }</div><div class="slate-code_line">}</div><div class="slate-code_line"></div><div class="slate-code_line">const key = &quot;&lt;YOUR-SALT-KEY&gt;&quot;;</div><div class="slate-code_line">const data = &quot;&lt;ENCRYPTED-TOKEN-FROM-CALLBACK&gt;&quot;;</div><div class="slate-code_line">decrypt(key, data).then(decryptedText =&gt; {</div><div class="slate-code_line">    console.log(&quot;Decryption:&quot;, decryptedText);</div><div class="slate-code_line">});</div></code></pre><p class="slate-p" placeholder="Type / for widgets">Below is the Java function that you can use to decrypt an encrypted callback response:</p><pre class="slate-CodeBlockElement slate-code_block"><div contenteditable="false"><div ><span aria-live="polite" aria-atomic="false" aria-relevant="additions text" ></span><div ><div ><div >Select...</div><div ><div  style="display:inline-block"><input type="text" autoCapitalize="none" autoComplete="off" autoCorrect="off" id="react-select-21-input" spellcheck="false" tabindex="0" value="" aria-autocomplete="list" style="box-sizing:content-box;width:1px;label:input;background:0;border:0;font-size:inherit;opacity:1;outline:0;padding:0;color:inherit"/><div style="position:absolute;top:0;left:0;visibility:hidden;height:0;overflow:scroll;white-space:pre"></div></div></div></div><div ><span ></span><div  aria-hidden="true"><svg height="20" width="20" viewBox="0 0 20 20" aria-hidden="true" focusable="false" ><path d="M4.516 7.548c0.436-0.446 1.043-0.481 1.576 0l3.908 3.747 3.908-3.747c0.533-0.481 1.141-0.446 1.574 0 0.436 0.445 0.408 1.197 0 1.615-0.406 0.418-4.695 4.502-4.695 4.502-0.217 0.223-0.502 0.335-0.787 0.335s-0.57-0.112-0.789-0.335c0 0-4.287-4.084-4.695-4.502s-0.436-1.17 0-1.615z"></path></svg></div></div></div></div></div><code class="language-java keep-markup drop-tokens"><div class="slate-code_line">import javax.crypto.spec.IvParameterSpec;</div><div class="slate-code_line">import javax.crypto.spec.SecretKeySpec;</div><div class="slate-code_line">import javax.crypto.Cipher;</div><div class="slate-code_line">import java.util.Base64;</div><div class="slate-code_line">import java.security.SecureRandom;</div><div class="slate-code_line">class Java_AES_Cipher {</div><div class="slate-code_line">    private static final String CIPHER_NAME = &quot;AES/CBC/PKCS5Padding&quot;; // Use PKCS5Padding for compatibility with PHP
</div><div class="slate-code_line">    private static int CIPHER_KEY_LEN = 16; //128 bits</div><div class="slate-code_line">    public String decrypt(String key, String data) {</div><div class="slate-code_line">        try {</div><div class="slate-code_line">            String[] parts = data.split(&quot;:&quot;);</div><div class="slate-code_line">            byte[] ivBytes = Base64.getDecoder().decode(parts[1]);</div><div class="slate-code_line">            byte[] encryptedData = Base64.getDecoder().decode(parts[0]);</div><div class="slate-code_line">            IvParameterSpec iv = new IvParameterSpec(ivBytes);</div><div class="slate-code_line">            SecretKeySpec skeySpec = new SecretKeySpec(key.getBytes(&quot;UTF-8&quot;), &quot;AES&quot;);</div><div class="slate-code_line">            Cipher cipher = Cipher.getInstance(CIPHER_NAME);</div><div class="slate-code_line">            cipher.init(Cipher.DECRYPT_MODE, skeySpec, iv);</div><div class="slate-code_line">            byte[] original = cipher.doFinal(encryptedData);</div><div class="slate-code_line">            return new String(original);</div><div class="slate-code_line">        } catch (Exception ex) {</div><div class="slate-code_line">            ex.printStackTrace();</div><div class="slate-code_line">        }</div><div class="slate-code_line">        return null;</div><div class="slate-code_line">    }</div><div class="slate-code_line">    public static void main(String args[]) {</div><div class="slate-code_line">        Java_AES_Cipher ciph = new Java_AES_Cipher();</div><div class="slate-code_line">        // ciph.generateKey();
</div><div class="slate-code_line">        System.out.println(&quot;Decryption : &quot; + ciph.decrypt(&quot;&lt;YOUR-SALT-KEY&gt;&quot;, &quot;&lt;ENCRYPTED-TOKEN-FROM-CALLBACK&gt;&quot;));</div><div class="slate-code_line">    }</div><div class="slate-code_line">}</div></code></pre><p class="slate-p" placeholder="Type / for widgets">Below is the PHP function that you can use to decrypt an encrypted callback response:</p><pre class="slate-CodeBlockElement slate-code_block"><div contenteditable="false"><div ><span aria-live="polite" aria-atomic="false" aria-relevant="additions text" ></span><div ><div ><div >Select...</div><div ><div  style="display:inline-block"><input type="text" autoCapitalize="none" autoComplete="off" autoCorrect="off" id="react-select-22-input" spellcheck="false" tabindex="0" value="" aria-autocomplete="list" style="box-sizing:content-box;width:1px;label:input;background:0;border:0;font-size:inherit;opacity:1;outline:0;padding:0;color:inherit"/><div style="position:absolute;top:0;left:0;visibility:hidden;height:0;overflow:scroll;white-space:pre"></div></div></div></div><div ><span ></span><div  aria-hidden="true"><svg height="20" width="20" viewBox="0 0 20 20" aria-hidden="true" focusable="false" ><path d="M4.516 7.548c0.436-0.446 1.043-0.481 1.576 0l3.908 3.747 3.908-3.747c0.533-0.481 1.141-0.446 1.574 0 0.436 0.445 0.408 1.197 0 1.615-0.406 0.418-4.695 4.502-4.695 4.502-0.217 0.223-0.502 0.335-0.787 0.335s-0.57-0.112-0.789-0.335c0 0-4.287-4.084-4.695-4.502s-0.436-1.17 0-1.615z"></path></svg></div></div></div></div></div><code class="language-php keep-markup drop-tokens"><div class="slate-code_line">&lt;?php

function decrypt($key, $data) {
    try {
        $parts = explode(&quot;:&quot;, $data);
        $iv = base64_decode($parts[1]);
        $encryptedData = base64_decode($parts[0]);</div><div class="slate-code_line">        // Decrypt the data
</div><div class="slate-code_line">        $decryptedData = openssl_decrypt($encryptedData, &apos;aes-128-cbc&apos;, $key, OPENSSL_RAW_DATA, $iv);</div><div class="slate-code_line">        return $decryptedData;</div><div class="slate-code_line">      } catch (Exception $ex) {</div><div class="slate-code_line">        error_log($ex-&gt;getMessage());</div><div class="slate-code_line">        return null; // Or handle the error as per your requirement
</div><div class="slate-code_line">      }</div><div class="slate-code_line">    }

$key = &quot;&lt;YOUR-SALT-KEY&gt;&quot;; // Ensure this is the correct key for decryption
$data = &quot;&lt;ENCRYPTED-TOKEN-FROM-CALLBACK&gt;&quot;; // The encrypted data you need to decrypt

$decryptedText = decrypt($key, $data);

echo &quot;Decryption: &quot; . $decryptedText . &quot;\n&quot;;

?&gt;

</div></code></pre><p class="slate-p" placeholder="Type / for widgets"></p>

When certain API requests are made, a callback response may be sent to a specified URL to inform your application about the status or result of the request. This section details the structure, types, and handling of callback responses from our API.

Before you can receive callback responses, ensure you have set up and provided a callback URL in your API request. The callback have to be in POST method, so that you will receive the callback properly.

Callback responses typically contain a JSON payload with a standard structure. This structure may include, but is not limited to, the following fields:

If your callback responses are encrypted for enhanced security, you must decrypt them to access the actual data. This section outlines the decryption process based on the encryption method used by our API.

Encrypted callbacks ensure sensitive information is securely transmitted. Only parties with the correct decryption key can access the original data, protecting it from unauthorized access or eavesdropping.

Our API uses the following encryption method for callback responses:

Below is the JavaScript function that you can use to decrypt an encrypted callback response:

Below is the Java function that you can use to decrypt an encrypted callback response:

Below is the PHP function that you can use to decrypt an encrypted callback response:

status

token

<p>This API is designed specifically for mobile applications to integrate a payment button, enabling a seamless redirection to the payment application installed on the user's device. Follow the outlined steps below for comprehensive guidance on integration and customization.</p><p><strong>Follow the below steps to complete </strong></p>

This API is designed specifically for mobile applications to integrate a payment button, enabling a seamless redirection to the payment application installed on the user's device. Follow the outlined steps below for comprehensive guidance on integration and customization.

: After successfully creating a transaction, you'll use the upi_url from the response in your website or mobile application to redirect the user to their payment application to complete the transaction.

<p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">1 . Where to find the saltKey or API key?</strong></p><p class="slate-p slate-indent-1" style="margin-left:24px" placeholder="Type / for widgets">Login into your account → Go to “Account Settings” → Check “View Api Key”/ “View Salt Key”</p><p class="slate-p" placeholder="Type / for widgets"><strong class="slate-bold">2. How long it will take to verify the transaction? </strong></p><p class="slate-p slate-indent-1" style="margin-left:24px" placeholder="Type / for widgets"> After the transaction initiated, it will take 15 to 20mins. if still not verified, please contact our support team. </p><p class="slate-p" placeholder="Type / for widgets"></p>

1 . Where to find the saltKey or API key?

Login into your account → Go to “Account Settings” → Check “View Api Key”/ “View Salt Key”

2. How long it will take to verify the transaction? 

 After the transaction initiated, it will take 15 to 20mins. if still not verified, please contact our support team. 