Body
Authorization Data API
Juspay / JusBiz will be pushing the authorization details for every Virtual Card to Corporate using an Auth API webhook. In order to get access to the auth details, Corporate needs to share the below details with Juspay:
Note
Please go through the Webhooks module under Resources section to know more about webhooks.
Webhook URL on which JusBiz will push the auth data to the Corporate
Webhook authorization key - a) username and b) password
Please note:
Please refer the sample request body.
This request will be encrypted using Corporate provided encryption key:
While uploading the RSA Key, corporate will have to select the type of key and define if key is to be used for API auth or for encryption. This will be done on the JusBiz dashboard.
Corporate should store the keyUUID as it will be part of the headers.
This request will also be signed by Juspay. In order to verify, please download the public key from the JusBiz dashboard. You may reach out to your JusBiz POC for further details or queries.
Request
Response
API Endpoints
Production Link
POST
Webhook URL Provided by Corporate
Headers
keyUuid
*
string
Mandatory
Example:- keyUuid is the Key Id against which encryption is done. Juspay to provide when public key is shared by Merchant.
cardAlias
String
Optional
Example:- cardAlias is the name given to the primary card on the dashboard. It can be used to identify the primary card for which the callback has been received.
Webhook Request
rqstType
*
String
Mandatory
Denotes the status of authorization. It can have following values:
AuthorizationSuccess
AuthorizationFailure
AuthorizationReversal
payoutId
Optional
Boolean
Unique value of payout id which was sent in the request.
payoutAmnt
*
String
Mandatory
Total Amount = This is sum of orderAmount + gst
payoutCurrCd
*
String
Mandatory
Currency of the payout
tranId
*
String
Mandatory
Unique transaction ID assigned to transaction
authTime
*
String
Mandatory
DateTime on which transaction was made at point of sale,
Format: timestamp is in UTC
tranAmnt
*
String
Mandatory
Amount that was sent for payment authorization
tranCurrCd
*
String
Mandatory
Currency code in which the card was redeemed
merchCatgCd
*
String
Mandatory
Merchant category code of the beneficiary who redeemed the Virtual Card
mrchCity
*
String
Mandatory
City of the beneficiary who redeemed the Virtual Card
mrchName
*
String
Mandatory
Name of the beneficiary who redeemed the Virtual Card
lastFourTokenNumber
*
String
Mandatory
Contains the last four digits of the token number.
lastFourCardNumber
*
String
Mandatory
Contains the last four digits of the primary card number.
errMsg
*
String
Mandatory
Error message in case transaction was unsuccessful
cardAlias
*
String
Mandatory
A unique alias to identify the card - juspay creates this alias during the funding pan addition.
200 : Success
Response Body
200: Response Body
Object
When authorizations are successfully processed by client’s endpoint, a HTTPS status code of 200 should be sent back to Juspay.
400 : Invalid Input data
Response Body
400: Response Body
Object
This status code indicates there was an incorrectly formatted authorization push notification sent by Juspay.
500 : Unexpected Error
Response Body
500: Response Body
Object
This status code indicates client services are unavailable.
Have questions?
- Need help? Contact support
- LLM? Read llms.txt