Update Session Token
In some cases flow is needed to be continued even when signature expires, so it generates the need for communication between Juspay sdk and merchant to continue flow with new signature, provided by merchant. The solution to the above issue is providing a callback to the merchant, indicating signature expiry and requesting a new token.
Input (Payload) Details
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 updateAuth for this call
Example:- updateAuth
Default 15min (to extend functionality later if configuration to change signature expiry will be added)
Base 64 encoding of signaturePayload 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
Base 64 encoded stringified signature payload
Unique identifier associated with an account created by juspay.Ex: stock
Merchant generated unique profile id for the customer.
As provided by Juspay.
Time when request is created in milliseconds.
Example: 1665996901100
This event is given when clientAuthToken/signature expires. This event will be received by merchant under `onEvent` callbacks from Juspay's SDK with the event name `session_expired` and a `reqCode`.
{ "event":"session_expired",
"payload":
{ "timestamp": "2021-07-19T07:20:53.318Z",
"reqCode" : "gdjhsdfgjhf-dsfyfsudgk"
}
}