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

Method

Parameter Type

URL

cf_subReferenceId

Long

Unique Id which was generated when the subscription was created (Numeric)

cf_subscriptionId

String

Checksum used to authenticate the transaction

cf_authAmount

Float

The money that was charged to authorize the subscription

cf_referenceId

Long

The referenceId/transactionId of authorization in PG

cf_status

String

Status 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_message

String

A brief note about the payment.

signature

String

The hash of all parameters in the request generated using secretKey.

cf_umrn

String

The unique identifier associated with a mandate. Applicable if the payment mode is eMandate.

cf_checkoutStatus

String

The 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_mode

String

The 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_subscriptionPaymentId

String

The subscription payment ID.

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