ClientAuthToken vs Signature
The APIs in the doc follow a common top level structure for each request and response body with a common outer payload and an API specific inner payload.
Unique uuid-v4 string
Example: abcd-12345-abcd-12345
Value: in.juspay.hyperapi
Parameters required to call Hyper SDK API
Each Inner Payload must contain one of the two authentication field group:
In the inner payload, only one of the below details is required to be passed. In case payload Signature Support is being passed in the request already, there is no need to pass clientAuthToken in the payload.
Unique uuid-v4 string
Example: abcd-12345-abcd-12345
Value: in.juspay.hyperapi
Parameters required to call Hyper SDK API
Key ID to identify the public-private key pair used for signature generation.
Signature generated for the signaturePayload.
Parameters required to call Hyper SDK API
Unique identifier associated with an account created by juspay.
Example: stock
Any unique reference associated with your customer.
Time when request is created in milliseconds.
Unique uuid-v4 string
Example: abcd-12345-abcd-12345
Value: in.juspay.hyperapi
Parameters required to call Hyper SDK API
clientAuthToken
Unique identifier associated with an account created by juspay.
Example: stock
Any unique reference associated with your customer.
For a clientAuthToken-based payload, you need to make several changes in the signature-based payload.
First, remove the keys "merchantKeyId," "signature," and "signaturePayload" from the payload. These keys are no longer necessary.
Next, focus on the contents of the "signaturePayload" key. Change all the key names inside the "signaturePayload" object to adhere to the camel case convention. For example, if you have a key named "merchant_id", change it to "merchantId". Apply this transformation to all the keys inside the "signaturePayload" object.
Once you have modified the key names, add them to the "payload" object. You can eliminate the "timestamp" key as well. Refer the below example.
Unique uuid-v4 string
Example:- $requestId
Value: in.juspay.hyperapi
Parameters required to call Hyper SDK API
Operation to be performed in the SDK. Should be initiate for this call.
Example:- Value: initiate
Client Id assigned by juspay. Usual convention is merchant_id
Example: stock
Environment to be used for the session. Accepted values are 'sandbox' or 'production'
Example: sandbox
Bank on which the merchant has been onboarded.
Example: YES_BIZ
Key ID to identify the public-private key pair used for signature generation.
Example: 1234
Generated signature for signature payload. See signature generation process in pre-requisites section.
Signature payload is a stringified JSON of the details mentioned in the below table.
Unique identifier associated with an account created by juspay.
Example: stock
Any unique reference associated with your customer.
Example: abcde12345
Time when request is created in milliseconds.
Example: 1665996901100
Unique uuid-v4 string
Example:- $requestId
Value: in.juspay.hyperapi
Parameters required to call Hyper SDK API
Operation to be performed in the SDK. Should be initiate for this call.
Example:- Value: initiate
Client Id assigned by juspay. Usual convention is merchant_id
Example: stock
Environment to be used for the session. Accepted values are 'sandbox' or 'production'
Example: sandbox
Bank on which the merchant has been onboarded.
Example: YES_BIZ
Unique identifier associated with an account created by juspay.
Example: stock
Any unique reference associated with your customer.
Example: abcde12345
clientAuthToken

