Prerequisites

Before starting the integration, ensure you have the following details:

1. Merchant Credentials

  • Merchant ID: Unique identifier for API calls, provided by Juspay. For new Merchant ID creation, please reach out to us herelink icon.

  • Client ID: Used for SDK-based requests, usually the same as the Merchant ID.

2. Juspay Dashboard Access

Create a Juspay Merchant Account : Obtain dashboard access (Sandbox/Production) via Juspay or your Business SPOC.

  • Sign up to create your Sandboxlink icon / Productionlink icon merchant account.

  • Your account starts in Restricted Mode, which supports test transactions only.

Note

During onboarding, your production account operates in Restricted Mode, which limits the number and value of transactions. This restriction is lifted after successful integration and QA signoff from Juspay.

Refer Unified Juspay Dashboard Guidelink icon that covers essential configurations, including:

  • Gateway setup

  • Security key generation

  • Webhook URL configuration

  • Payment instrument enablement/disablement

  • Batch operations & traffic monitoring and analytics

3. Get Gateway Credentials

Reach out to your respective payment gateway provider (e.g., 2C2P, Airwallex) and obtain:

  • Merchant ID

  • Client ID

  • API Keys or Tokens

These are necessary for enabling payment flows in the production environment.

Note

Don’t have live Gateway Credentials?

You can test your integration using Juspay’s Dummy Gateway.

Juspay Dummy Gateway?

A Dummy Gateway is a mock payment gateway provided by Juspay to simulate transaction responses. It supports multiple payment methods and allows you to test various payment statuses and flows.

Usage Guidelines:

  • Use only in UAT / Sandbox environments

  • Do not use in Production

4. API Key

Juspay uses HTTP Basic Auth for API authentication. An API Key is required for secure server-to-server communication.

API Key Generation using Juspay Dashboard
Note

The API request requires a Basic Authorization header.

To generate it, append a colon (:) to your API Key and Base64-encode the resulting string.

  • API Key: 1cc33A5F5D6aa54AB20CF6FbbC8558

  • Encoding Format:
    Combine your API Key with a colon (:) at the end:
    1cc33A5F5D6aa54AB20CF6FbbC8558:

  • Base64 Encoded API Key:
    MWNjMzNBNUY1RDZhYTU0QUIyMENGNkZiYkM4NTU4Og==

Last updated 9 months ago