UPI Management with UI
1. UPI Profile Management
This operation supports all UPI Profile management features.
Unique uuid-v4 string
Example: abcd-12345-abcd-12345
value: in.juspay.hyperapi
Parameters required to call Hyper SDK API
Operation to be performed in the SDK to open the management screen.
Example:- value: management
Protected payload is a stringified JSON of the details mentioned in the below table.
Key ID to identify the public-private key pair used for signature generation.It will be provided to you by the Juspay team.
Example: uat833359804655gg748702e324111
Algorithm to generate JWS signature in respect to base 64.
Example:- RS256
Signature generated for the signaturePayload.
Base 64 encoded stringified signature payload
Unique identifier associated with an account created by juspay.
Example: stock
Merchant generated unique profile id for the customer.
Example: abcde12345
As provided by Juspay.
Example: ade123
Time when request is created in milliseconds.
Example: 1665996901100
2. UPI Incoming Intent for Collect
This operation will enable the merchant app to accept incoming UPI Intent requests from other apps.
Unique uuid-v4 string
Example: abcd-12345-abcd-12345
value: in.juspay.hyperapi
Parameters required to call Hyper SDK API
Operation to be performed in the SDK. Should be incomingIntent for this call.
Example:- value: incomingIntent
It will be provided by the app triggering the merchant app for UPI transaction
Base 64 encoded with signature payload and protected.
Base 64 encoding of the below parameters.
Key ID to identify the public-private key pair used for signature generation.It will be provided to you by the Juspay team.
Example: uat833359804655bb748702e324111
Asymmetric algorithm used. Will be RS256 in this case..
Example:- RS256
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
Merchant Channel Id as shared by juspay.
Example: stock
3. Approve UPI Collect
This operation will enable the merchant app to accept incoming UPI Collect requests from other apps. A merchant server endpoint will be configured on the axis backend. Hook will be triggered to the merchant server, which should be integrated to the merchant app GCM/FCM.
Unique uuid-v4 string
Example: abcd-12345-abcd-12345
value: in.juspay.hyperapi
Parameters required to call Hyper SDK API
Operation to be performed in the SDK. Should be approveCollect for this call.
Example:- Value: approveCollect
It will be provided by the app triggering the merchant app for UPI transaction. It should be base64 encrypted
Generated signature for signature payload and protected base 64 encoded.
Base 64 encoding of the below parameters.
Key ID to identify the public-private key pair used for signature generation.It will be provided to you by the Juspay team.
Example: uat833359804655bb748702e324111
Asymmetric algorithm used. Will be RS256 in this case..
Example:- RS256
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
Channel Id of the merchant as shared by juspay.
Example: stock
UPI request id returned by gateway for the transaction
Example: ABC123456789
4. UPI Incoming Intent for Mandate
This operation will enable the merchant app to accept incoming UPI Intent requests from other apps.
Unique uuid-v4 string
Example: abcd-12345-abcd-12345
value: in.juspay.hyperapi
Parameters required to call Hyper SDK API
Operation to be performed in the SDK. Should be incomingIntent for this call.
Example:- Value: incomingMandate
It will be provided by the app triggering the merchant app for UPI transaction
Generated signature for signature payload.
Base 64 encoding of the below parameters.
Key ID to identify the public-private key pair used for signature generation.It will be provided to you by the Juspay team.
Example: uat833359804655bb748702e324111
Asymmetric algorithm used. Will be RS256 in this case..
Example:- RS256
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
Channel Id as provided by juspay.
Example: stock
Pass false to hide payment status screen. Default value: true
Example:- Possible values: true/false
5. Approve UPI Mandate
This operation will enable the merchant app to accept incoming UPI Mandate requests from other apps. A merchant server endpoint will be configured on the axis backend. Hook will be triggered to the merchant server, which should be integrated to the merchant app GCM/FCM.
Unique uuid-v4 string
Example: abcd-12345-abcd-12345
value: in.juspay.hyperapi
Parameters required to call Hyper SDK API
Operation to be performed in the SDK. Should be approveMandate for this call.
Example:- Value: approveMandate
Details of the incoming mandate from the webhook
Example: abc12345
Generated signature for signature payload. See signature generation process in pre-requisites section.
Base 64 encoding of the below parameters.
Key ID to identify the public-private key pair used for signature generation.It will be provided to you by the Juspay team.
Example: uat833359804655bb748702e324111
Asymmetric algorithm used. Will be RS256 in this case..
Example:- RS256
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
Channel Id provided by juspay.
Example: stock