Server-to-Server Documentation

Introduction

This document provides details on the Payment Gateway API, which allows merchants to process and manage transactions securely. The API supports:

  • 3D Secure (3DS) transactions for authentication and authorization.
  • Transaction authorization via OTP verification.
  • Transaction status verification to track payments.
  • Industry-standard security protocols for safe transaction processing.

All API requests must be made using HTTPS and include authentication headers.


Authentication & Security

API Authentication

  • All requests must be initiated from the server to protect the merchant’s private key.
  • Requests must originate from whitelisted IP addresses associated with the private key.

Security Headers

These headers must be included in all API requests:

KeyValueRequiredDescription
Authorization{PRIVATE_KEY}YesThe merchant’s private key used for authentication.
Content-Typeapplication/jsonYesSpecifies that the request body is in JSON format.

Note:


What’s Next