Redirection Payload after Authorization

When a subscription is created a returnUrl is provided as a part of the request. When the customer authorizes the payment, they will be redirected to the returnURL. This redirection is done via a POST request with the parameters available below.

Request Configuration

MethodParameter TypeURL
cf_subReferenceIdLongUnique Id which was generated when the subscription was created (Numeric)
cf_subscriptionIdStringChecksum used to authenticate the transaction
cf_authAmountFloatThe money that was charged to authorize the subscription
cf_referenceIdLongThe referenceId/transactionId of authorization in PG
cf_statusStringStatus of the subscription. In the returnUrl, the response should be ACTIVE or BANK_APPROVAL_PENDING if the authorization was successful or INITIALIZED if the authorization failed.
cf_messageStringA brief note about the payment.
signatureStringThe hash of all parameters in the request generated using secretKey.
cf_umrnStringThe unique identifier associated with a mandate. Applicable if the payment mode is eMandate.
cf_checkoutStatusStringThe subscription checkout status. The status can be SUCCESS, FAILED, SUCCESS_DEBIT_PENDING, SUCCESS_TOKENIZATION_PENDING

(This parameter will be sent from the 1st of November onwards, by default. It is available in the test environment.)
cf_modeStringThe checkout payment mode. Modes - NPCI_SBC, SBC_UPI, SBC_CREDIT_CARD,
SBC_DEBIT_CARD


(This parameter will be sent from the 1st of November onwards, by default. It is available in the test environment.)
cf_subscriptionPaymentIdStringThe subscription payment ID.

(This parameter will be sent from the 1st of November onwards, by default. It is available in the test environment.)