1. HASH
Sipay API Documentation
  • Overview
    • Getting Started
  • Authentication
    • Token Generation
      POST
  • Installments & Commission
    • Installment Details
      POST
    • Merchant Installments
      POST
    • Commission
      POST
  • HASH
    • Hash Creation
    • Hash Validation
  • Non - Secure Payment
    • Non-Secure Payment Flow
    • Non-Secure Card Payment
      POST
    • Non-Secure Recurring Payment
      POST
    • Non-Secure Insurance Payment
      POST
    • Non-Secure Pre-Authorization Payment
      POST
    • Confirm Payment
      POST
  • 3D Secure Payment
    • 3D Secure Payment Flow
    • 3D Secure Card Payment
      POST
    • 3D Secure Recurring Payment
      POST
    • 3D Secure Pre-Authorization Payment
      POST
    • Complete Payment
      POST
    • Confirm Payment
      POST
    • 3D Secure Agriculture Payment
      POST
  • Non-Secure and 3D Payment with Sipay
    • Non-Secure and 3D Payment with Sipay
      POST
  • Check Status
    • Check Status
      POST
  • Payment with Saved Card
    • Card Registration
    • 3D Secure Pay by Card Token
    • Non-Secure Pay by Card Token
    • Retrieving Saved Card
    • Edit Saved Card
    • Delete Saved Card
  • Recurring
    • Recurring Query Search
    • Recurring Plan Process
    • Recurring Plan Update
  • Refund
    • Refund
  • Cashout
    • Cashout to Bank
  • Webhook
    • Webhook
  • Status Codes
    • Status Codes
  1. HASH

Hash Creation

This guide explains how to generate and use the hash key required for secure API communication. The hash mechanism ensures that requests are authenticated and have not been altered during transmission.
Hash_key should be obtained from the request, and secret_key is the merchant application's secret key (app_secret) provided by Sipay.
The hash key is a mandatory parameter and must be included in the request.
Required parameters may vary depending on the endpoint being used.
When the relevant endpoint is accessed and a preferred programming language is selected in the request section, a sample HASH implementation can be found and copied directly from there.
The following parameters must be sent in the same order as specified.

Important Notes#

Each request should generate a new hash key.
Ensure that all parameters are sent in the correct order.
Any mismatch in parameter values will result in hash validation errors.

Common Errors#

Incorrect parameter order.
Missing or null values.
Using different hash/encryption algorithms.
The same hash key algorithm and parameters can be used for payment transactions (ex: Non Secure and 3DS Payment.)

📌

The parameters required to decrypt the hash are as follows:#

hash_key
app_secret
Modified at 2026-04-22 11:54:18
Previous
Commission
Next
Hash Validation
Built with