Modify Recurring Payments of Cards

Use this endpoint to modify recurring payments and mandates of cards of the following card networks. You can update mandate details, recurring payment configurations, billing rules, and subscription settings for active recurring transactions.

Visa
Mastercard
Amex
RuPay

❗️
RBI Guidelines:
While modifying the recurring payment, taking consent from the customer and doing an additional factor of authentication is mandatory. You must ensure this is done before using this API. You need to pass authPayuId and action parameters to modify the billing details as a part of JSON using this API.

Method

POST

Endpoint

/_payment

Sample Request

Request Payload

  curl --location 'https://test.payu.in/_payment' \
  --header 'accept: application/json' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'Cookie: PHPSESSID=jp38t4gvop7ami1ksncksj398v; USERTXNINFO=68ed4df291d9b7.27710642; PHPSESSID=68edd726c95b4' \
  --data-urlencode 'key=BmTY3G' \
  --data-urlencode 'txnid=my_order_47719' \
  --data-urlencode 'amount=1.00' \
  --data-urlencode 'firstname=Gaurav' \
  --data-urlencode '[email protected]' \
  --data-urlencode 'phone=1234567890' \
  --data-urlencode 'productinfo=my_order_47719' \
  --data-urlencode 'api_version=7' \
  --data-urlencode 'si=3' \
  --data-urlencode 'pg=CC' \
  --data-urlencode 'bankcode=UTIBENCC' \
  --data-urlencode 'surl=https://test.payu.in/admin/test_response' \
  --data-urlencode 'furl=https://test.payu.in/admin/test_response' \
  --data-urlencode 'ccnum=5123456789012346' \
  --data-urlencode 'ccexpmon=05' \
  --data-urlencode 'ccexpyr=2030' \
  --data-urlencode 'ccvv=123' \
  --data-urlencode 'ccname=Test User' \
  --data-urlencode 'si_details={"action":"modify","paymentEndDate":"2030-04-13","billingAmount":"400.00","authPayuId":"999990000006391"}' \
  --data-urlencode 'hash=YOUR_HASH_VALUE'

Sample Response

Response Payload

Array
(
    [mihpayid]         => 25603951365
    [mode]             => CC
    [status]           => success
    [unmappedstatus]   => captured
    [key]              => BmTY3G
    [txnid]            => 5527fc7d02f2bfc00eb4
    [amount]           => 1.00
    [cardCategory]     => signature_premium
    [discount]         => 0.00
    [net_amount_debit] => 1
    [addedon]          => 2025-10-14 15:44:41
    [productinfo]      => Product Info
    [firstname]        => Payu-Admin
    [lastname]         => 
    [address1]         => 
    [address2]         => 
    [city]             => 
    [state]            => 
    [country]          => 
    [zipcode]          => 
    [email]            => [email protected]
    [phone]            => 1234567890
    [udf1]             => 
    [udf2]             => 
    [udf3]             => 
    [udf4]             => 
    [udf5]             => 
    [udf6]             => 
    [udf7]             => 
    [udf8]             => 
    [udf9]             => 
    [udf10]            => 
    [hash]             => YOUR_HASH_VALUE
    [field1]           => CBC10141015051509EGR573
    [field2]           => 185869
    [field3]           => 
    [field4]           => 
    [field5]           => 
    [field6]           => 05
    [field7]           => AUTHPOSITIVE
    [field8]           => 0 | Transaction Completed
    [field9]           => Transaction Completed
    [payment_source]   => payu
    [meCode]           => {
                                "wibmo_merchant_id":"16329672",
                                "hash_key":"YOUR_HASH_VALUE",
                                "acquirer_merchant_id":"175645866049780",
                                "mcc":"5499"
                            }
    [PG_TYPE]          => CC-PG
    [bank_ref_num]     => 528710004895
    [bankcode]         => CC
    [error]            => E000
    [error_Message]    => No Error
    [cardnum]          => XXXXXXXXXXXX4879
)

Request Parameters

📘
Mandatory Parameters
Parameters marked with are mandatory.

Parameter	Description
`key`	`varchar` The unique Merchant Key provided by PayU for your merchant account.
`txnid`	`varchar` A unique transaction ID (or order ID). It is the order reference number generated at your end. You can use this ID to track a particular order. This ID should be unique and you can duplicate it. The parameter value can be maximum of 25 characters.
`amount`	`float` The transaction amount in `INR`. Note: Type-cast the amount to float type Depending upon the merchant use case, this value will vary. The value should be minimum of `1.00` INR for Cards for penny testing. For first installment, this can be initiate setup amount However, this is supported only for selected NetBanking (ICICI and HDFC), all Credit / Debit Cards, and UPI.
`firstname`	`varchar` The first name of the customer. For example, `Gaurav`. The value can contain maximum of 60 characters.
`email`	`varchar` The email of the customer. For example, `[email protected]`. The value can contain maximum of 50 characters. Note: The email is used in case of fraud detection and chargebacks. Additionally, MIS reporting is shared with few issuing banks where email and mobile number is used to keep track of users using SI transactions.
`phone`	`varchar` The customer phone number. For example, `1234567890`. Note: The email is used in case of fraud detection and chargebacks. Additionally, MIS reporting is shared with few issuing banks where email and mobile number is used to keep track of users using SI transactions.
`productinfo`	`string` A product description. The value can contain maximum of 100 characters.
`api_version`	`number` The API version. You should always pass this value as `7`.
`si`	`number` The standing instruction. You should pass the value as `3` to modify the card mandate.
`pg`	`string` This parameter describes the payment category by which the transaction was completed/attempted by the customer. Possible values: `DC`: For debit cards `CC`: For credit cards
`bankcode`	`string` This parameter contains the code indicating the payment option used for the transaction. Possible values: `CC`: For Visa and Mastercard credit cards `AMEX`: For American Express credit and debit cards `RUPAYCC`: For RuPay credit cards `VISA`: For Visa debit cards `MAST`: For Mastercard debit cards `RUPAY`: For RuPay debit cards
`surl`	`string` The success URL customers are redirected to if the transaction is successful.
`furl`	`string` The failure URL customers are redirected to if the transaction is unsuccessful.
`ccnum`	`number` The credit card number used to register the mandate.
`ccexpmon`	`number` The expiry month of the CC.
`ccexpyr`	`number` The expiry year of the CC.
`ccvv`	`number` The CVV of the CC.
`ccname`	`string` The name of the CC owner.
`si_details`	`json` The SI mandatory details that need to be passed during registration transaction from your system to PayU. Parameters are described in the si_details Object section.
`hash`	`string` The calculated hash value using the following logic. `SHA512(key\|txnid\|amount\|productinfo\|firstname\|email\|udf1\|udf2\|udf3\|udf4\|udf5\|\|\|\|\|\|si_details\|SALT)`. You can use the below button to generate a hash by providing the parameter values as per the logic.

si_details JSON Parameters

📘
Handy Tips:

One or more fields (marked optional) in the following table must be posted to modify the subscription:

billingCycle

billingInterval

billingAmount

If the request was to modify a subscription, si_consent_action parameter needs to be validated in the response. The field must return values modify based on the action sent in billing details JSON. Also, the payment source returned in such cases will be payu.

Parameter	Description
`action`	`string` This field is used to modify or cancel an existing subscription. Pass `modify` as a value to modify a subscription.
`paymentEndDate`	`date` The end date of the billing plan in the YYYY-MM-DD format. Note: Make sure to pass the correct end date. Depending on the start and end date, number of payment iterations are internally calculated and same is passed to acquirers or banks.
`billingAmount`	`number` The billing amount is passed in the XX format. In use cases where `billingCycle` = `ADHOC`, amount passed is treated as maximum amount since the billing amount and billing cycle varies as per the usage of the subscription service. In this case, the merchant is free to charge any amount for customer up to the amount specified in the defined subscription call.
`authpayuid` `mandatory for modifying subscription with cards`	This field is used only to modify an existing subscription/consent. You can modify the following details: `startDate` `endDate` `billing cycle` `billing interval` `billing amount`

Response Parameters

Parameter	Description
`mihpayid`	`string` It is a unique reference number created for each transaction at PayU's end which is used to identify a transaction in case of a refund.
`mode`	`string` This parameter describes the payment category by which the transaction was completed/attempted by the customer. The values are: `CC`: Credit Card `DC`: Debit Card
`bankcode`	`string` This parameter contains the code indicating the payment option used for the transaction. Possible values: `CC`: For Visa and Mastercard credit cards `AMEX`: For American Express credit and debit cards `RUPAYCC`: For RuPay credit cards `VISA`: For Visa debit cards `MAST`: For Mastercard debit cards `RUPAY`: For RuPay debit cards
`status`	`string` The status of the transaction and must be used to map the order status. Possible values: `success`: Indicates the transaction is successful. `failed/pending`: If the value is `failure` or `pending`, should be treated as a failed transaction.
`unmappedstatus`	`string` The status of a transaction in PayU's internal database, which can include intermediate states. Possible values: `dropped` `bounced` `captured` `auth` `failed` `usercancelled` `pending` Refer to the Payment State Explanations.
`key`	`string` The merchant key.
`error`	`string` The error reason in case of the failure transaction.
`error_message`	`string` The error message in case of the failure transaction.
`bank_ref_num`	`string` The bank reference number generated by the bank for successful transactions.
`txnid`	`string` The unique transaction ID value posted by the merchant during the transaction request.
`amount`	`float`The transaction amount sent in the request in INR.
`cardCategory`	`string` The card category to indicate whether it is domestic or international.
`discount`	`float` The discount amount.
`net_amount_debit`	`float` The net amount debited.
`addedon`	`datetime` The date and time of the transaction.
`productinfo`	`string` The product information sent in the request.
`firstname`	`string` The first name of the customer.
`lastname`	`string` The last name of the customer.
`email`	`string` The email address of the customer.
`phone`	`varchar` The phone number of the customer.
`hash`	`string` The hash value generated and sent in the request.
`PG_TYPE`	`string` Indicates the payment gateway used for the transaction.
`udf1-udf10`	`string` The user defined field values sent in the request.
`success_at`	`datetime` The date and time at when the transaction was successful.
`cardnum`	`integer` The last 4 digits of the card used for the transactions.
`issuing_bank`	`string` The card issuing bank.
`si_consent_action`	`string` This parameter will be returned only if a modify subscription request has been received. In other cases, this field will not be returned. Possible values: `modify` `cancel` If, in billing details, the action was to modify, then to validate whether the subscription was modified, this fields need to be validated in response. If this field is not sent in response of modify request, then even if transaction is success, then money would have got deducted but the subscription would not have been modified.

For Network Tokens

For si=3 (Modify or Cancel Mandate), PayU supports two integration flows based on how card details are processed:

Standard card flow
Network token flow

Use the standard card flow when processing mandates using regular card details. Use the network token flow when the card has been tokenized and the transaction must be processed using the network token instead of the physical card number.

📘
Handy Tips:
This scenario is applicable if you are PCI compliant and got the network token and TAVV from any other aggregator or schemes and then sent the card transaction request in the form of authentication.

Additional Object to Pass

Please find below the complete request payload with the additional added.

Sample Request Payload

curl --location 'https://test.payu.in/_payment' \
  --header 'accept: application/json' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'Cookie: PHPSESSID=jp38t4gvop7ami1ksncksj398v; USERTXNINFO=68ed4df291d9b7.27710642; PHPSESSID=68edd726c95b4' \
  --data-urlencode 'key=BmTY3G' \
  --data-urlencode 'txnid=my_order_47719' \
  --data-urlencode 'amount=1.00' \
  --data-urlencode 'firstname=Gaurav' \
  --data-urlencode '[email protected]' \
  --data-urlencode 'phone=1234567890' \
  --data-urlencode 'productinfo=my_order_47719' \
  --data-urlencode 'api_version=7' \
  --data-urlencode 'si=3' \
  --data-urlencode 'pg=CC' \
  --data-urlencode 'bankcode=UTIBENCC' \
  --data-urlencode 'surl=https://test.payu.in/admin/test_response' \
  --data-urlencode 'furl=https://test.payu.in/admin/test_response' \
  --data-urlencode 'storecard_token_type=1' \
  --data-urlencode 'storecard_token=5200000000000000001' \
  --data-urlencode 'additional_info_for_tokenized_flow={"tavv":"6726","last4digits":"1005","par":"A0009WTYMUG6ANFB3F9Z8CNYAKCX9"}' \
  --data-urlencode 'ccexpmon=05' \
  --data-urlencode 'ccexpyr=2030' \
  --data-urlencode 'ccname=Test User' \
  --data-urlencode 'si_details={"action":"modify","paymentEndDate":"2030-04-13","billingAmount":"400.00","authPayuId":"999990000006391"}' \
  --data-urlencode 'hash=YOUR_HASH_VALUE'

Additional Parameters

Parameter	Description
`store_card_token`	`string` The Network token generated by you.
`storecard_token_type`	`integer` Indicates the store card token type. For this scenario, you must include `1`.
`additional_info`	`json` This parameter will contain the additional information in the following JSON format: `{"last4Digits": "1234", "tavv": "ABCDEFGH","trid":"1234567890", "tokenRefNo":"abcde123456"}`

`additional_info` Object Parameters

Parameter	Description
`trid`	`string` (Token Requestor ID) is the identity given by the networks for creating the tokens. You should be able to get the same from your token provider.
`tokenRefNo`	`string` (Token Reference Number) is generated along with the network token. . You should be able to get the same from your token provider.
`TAVV`	`string` A token authentication verification value given by schemes or interchange. Also, known as cryptogram.

📘
Notes:

The last 4 digits of cards is mandatory for all transactions.

Some payment gateways require the Token Requester ID (trid) and Token Reference Number (tokenRefNo) to be passed for processing the transaction. Not passing these values will restrict the number of payment gateways available for processing the transaction.

Token Requester ID (trid) and Token Reference Number (tokenRefNo) are mandatory for Diners token transactions.

Sample Request

Sample Response

Request Parameters

Mandatory Parameters

si_details JSON Parameters

Handy Tips:

Response Parameters

For Network Tokens

Handy Tips:

Additional Object to Pass

Additional Parameters

additional_info Object Parameters

Notes:

EXAMPLE QUESTIONS

`additional_info` Object Parameters