Product Configuration Entity🔗
The Product entity consists of the following fields. You can find the JSON sample entity on the right side.
id-
stringThe unique identifier of a product generated by Razorpay for a sub-merchant account. This id is used to fetch or update a product. product_name-
stringThe product(s) to be configured. Possible values:payment_gatewaypayment_links
tnc-
objectIt consists of the configuration for the accepted terms and conditions by the merchant for the requested product. If the terms and conditions are accepted by the user for the requested product, it would consist of following fields:idstringThe unique identifier representing the acceptance of terms and conditions for a product by a user.acceptedbooleanThe flag that represents whether the terms and conditions are accepted by the user.accepted_atintegerThe Unix timestamp at which the terms and conditions were accepted by the user for the requested product.
activation_status-
stringThe status of the product activation.requestedneeds_clarificationunder_reviewactivatedsuspended
configuration-
The following are the possible configurations:
payment_methods-
objectThe payment methods configured, such as, netbanking, UPI, Wallet and EMI.upi-
objectThe UPI type payment method.statusstringThe status of UPI payment method.instrumentarrayThe list of UPI instruments requested or enabled.
netbanking-
objectThe netbanking type payment method.status-
stringThe status of the netbanking payment method. instrument-
arrayThe netbanking instrument object.instrument_typestringThe type of netbanking payment method. Possible values:
- Retail
- Corporate
- Retail
instrument_bankarrayThe list of netbanking banks requested or enabled. Refer the Appendix page for netbanking bank codes.
wallet-
objectThe Wallet type payment method.statusstringThe status of the Wallet payment method.instrumentarrayThe list of Wallet instruments requested or enabled.
emi-
stringThe EMI type payment method.status-
stringThe status of EMI payment method. instrument-
arrayThe EMI instrument object.typestringThe type of EMI payment method. Possible values:
- Retail
- Corporate
- Retail
partnerarrayThe list of EMI partners requested or enabled.
payment_capture-
objectThe payment capture settings object.modestringThe mode through which payment capture is done. Possible values:automatic: Payments are auto-captured (default)manual: You have to manually capture payments using our Capture API or from the Partner's Dashboard.
automatic_expirynumericThis denotes the time in minutes when the payment is in the authorized state. This is auto-captured.manual_expirynumericThis denotes the time in minutes until you can manually capture payments in the authorized state.- Must be equal to or greater than the
automatic_expire_periodvalue. - The default and the maximum value is 7200 minutes.
- The payments in the authorized state after the
manual_expire_periodare auto-refunded.
- Must be equal to or greater than the
settlements-
objectThe Settlement settings object.account_numberstringThe bank account number to which settlements are made. Account details can be found on the Partner's Razorpay Dashboard. For example, 7878780080316316ifsc_codestringThe IFSC associated with the bank account. For example,RATN0VAAPIS.beneficiary_namestringThe name of the beneficiary associated with the bank account.Handy Tip
This API parameter is needed complete the KYC process. However, it is optional for this API.
refund-
objectThis denotes the payment refund settings.default_refund_speedstringSpeed at which the refund is to be processed. Possible values are:- normal: Indicates that the refund will be processed at the normal speed. By default, the refund will take 5-7 working days.
- optimum: Indicates that the refund will be processed at an optimal speed based on Razorpay's internal fund transfer logic. That is:
- If the refund can be processed instantly, Razorpay will initiate the process irrespective of the payment method used to make the payment.
- If an instant refund is not made, Razorpay will initiate a refund that is processed at the normal speed. For example, payments made using debit cards, netbanking or unsupported credit cards.
checkout-
objectThe checkout form of the payment capture.theme_colorstringThe theme color for sub-merchant's checkout pagelogostringThe logo of the sub-merchant's business on the checkout page.flash_checkoutbooleanThe flagging options Enable or Disable for Razorpay's Flash Checkout to securely save the card details of your customers.
notifications-
objectThis denotes the notifications settings.emailstringThe email addresses that will receive notifications regarding payments, settlements, daily payment reports, webhooks, and so on.whatsappbooleanThe WhatsApp notifications you receive regarding payments, settlements, daily payment reports, webhooks, etc.smsbooleanThe SMS notifications you receive regarding payments, settlements, daily payment reports, webhooks, etc. This attribute will be set tofalse.
requested_configuration-
objectThe configuration of the product requested by the user that is yet to be set as active. active_configuration-
objectThe configuration of the product that has been set as active. requirements-
objectThe list of requirements to be enabled for this product or some of the configurations under this product.field_referencestringThe field which is in issue or missing. The JSON key path in resolution URL.resolution_urlstringThe URL to address the requirement. The API endpoint to be used for updating missing fields or documents.statusstringThe status of the requirement.reason_codestringThe reason code for showing in the requirement. Description will be sent only when reason code is "". Possible values are:field_missingneeds_clarificationdocument_missing
descriptionstringThis parameter is displayed when the reason_code isneeds_clarification.
requested_at-
integerThe Unix timestamp at which the product configuration is requested.