Authentication

💡

Please ensure that your IP address and email ID are whitelisted to avoid payment failures. If you haven’t already shared your IP or email with us, kindly do so at the earliest so we can add them to the whitelist.

Prerequisites

Before integrating with our APIs and Hosted Forms, ensure you have access to the following keys. These are essential for secure communication and proper handling of requests and responses between your systems and our platform.

You will need:

SECRET_KEY for encrypting payloads in Hosted Form payments.

API_KEY for authenticating API calls such as refunds, transfers, and other operations.

WEBHOOK_SECRET_KEY to validate the authenticity of incoming webhook events.

All keys provided here are sandbox credentials, intended for testing and development purposes only.

Secret Key

Example:
SK****************

Purpose:
Used for encrypting sensitive data before initiating hosted form payments. This key ensures that the payload is securely passed from your client-side integration to our platform.

Use Cases:

Hosted Form encryption

API Key

Example:
`AK****************``

Purpose:
Used to authenticate all direct API requests made from your server to our endpoints. These include transactional operations that require secure authorization.

Use Cases:

Initiating refunds

Creating internal transfers

Adjusting pre-authorizations

Reversing authorizations

Additional API-based features

Webhook Secret Key

Example:
WSK****************

Purpose:
Validates the authenticity of webhook events received from our platform. Each webhook will include a signature header that must be verified using this key.

Verification Flow:

Retrieve the signature from the incoming webhook header.

Generate a digest of the payload using your WEBHOOK_SECRET_KEY.

Compare your generated digest with the received signature to confirm authenticity.

Prerequisites#

Secret Key#

API Key#

Webhook Secret Key#

Prerequisites

Secret Key

API Key

Webhook Secret Key