168 Matching Annotations
  1. Apr 2023
    1. Given below is the sample payload for webhook events for Razorpay Optimizer. All the parameters and events will remain the same as shown in the sample payloads for payment webhooks except for one additional parameter, gateway_provider.

      You can use Razorpay Webhooks to configure and receive notifications when a specific event occurs. When an event is triggered, we send an HTTP POST payload in JSON to the webhook's configured URL.

      You can set up Webhooks from your Razorpay Dashboard

      Link it to https://betasite.razorpay.com/docs/razorpay/IN/optimizer-api-webhook-response/webhooks/setup-edit-payments

      Sample payload for webhook events for Optimizer. All the parameters and events will remain the same as shown in the sample payloads for payment webhooks except for one additional parameter, gateway_provider.

    2. Indicates the payment provider information.

      The payment provider used to process the payment. Possible values: payu cashfree paytm pinelabs ccavenue ingenico billdesk_optimizer

    3. API Response

      Payments API

      Payments APIs are used to capture and fetch payments. Payment entity has one extra field with Optimizer to identify the payment provider through which payment is processed.

    1. Given below are the supported payment providers and payment methods for Cards, Netbanking, UPI and Wallets.

      Given below are the supported payment providers and payment methods for Cards, Netbanking, UPI, EMI and Wallets.

    2. Razorpay Optimizer supports wallets for PayU, CCAvenue and Paytm. Know more about wallets supported by Razorpay.

      Optimizer supports wallets for Razorpay, PayU, CCAvenue and Paytm. Know more about wallets supported by Razorpay.

    1. Apart from the default rule, you can also create a set of custom rules for transactions. Also, you can set up priority levels. This means that if the success rate (SR) of a particular gateway assigned to Priority 1 drops below a certain level, all transactions will automatically be routed to the gateway assigned to Priority 2.

      You can create a set of custom rules for transactions using different parameters like Payment method, Card Type, and so on, add gateways in priority order, split traffic between gateways.

    1. In addition to standard and dynamic rule-based routing, Optimizer allows you to assign priority levels to all your transactions. This means that if the success rate (SR) of a particular gateway assigned to Priority 1 drops below a certain level, all transactions will automatically be routed to the gateway assigned to Priority 2, creating a temporary downtime for the gateway assigned to Priority 1. This ensures that payment processing remains smooth and uninterrupted for your customers, even if some payment gateways are experiencing issues. Once the temporary downtime is automatically resolved, that is, when the SR of the gateway assigned to Priority 1 retains a certain level, the transactions will be routed back to the gateway assigned to Priority 1.

      In addition to routing mechanisms explained above, Optimizer also allow you to add gateways in order of priority while creating custom rules. Our AI-ML algorithm monitors the traffic constantly and route the transactions to best performing gateway considering your priority order. Algorithm creates a temporary downtimes for 20 minute when SR reduces a particular threshold for high priority gateways and start routing transactions to next gateway as per the priority and its performance. This ensures that payment processing remains smooth and uninterrupted for your customers, even if some payment gateways are experiencing issues. For example, if the success rate (SR) of a gateway assigned to Priority 1 drops below a certain level, transactions will be automatically routed to the gateway configured at Priority 2.

      When the SR of the gateway assigned to higher priority retains a certain level, the transactions will be routed back to those gateways.

      Do vet the content from some else too to see others can also understand who don;t know the feature

  2. Mar 2023
    1. Watch Out!Manual Capture settings only apply to payments processed via Razorpay and do not apply to any external payment gateway.

      This is not required. We have complete separate section below for manual capture

    2. Watch Out! The time frame set for Manual Capture will not apply to payments processed via external gateways. Even if you have set a manual capture setting for any number of days, the payment will be auto-refunded as per the time frame set for Auto Capture. Manual Capture settings only apply to payments processed via Razorpay.
      • Manual Capture settings only apply to payments processed via Razorpay.

      • Optimizer will auto capture the payment if the payment is authorised within a certain time period.

      • Any payment authorised after that time period (auto capture time period) will be auto refunded.

      • Any manual capture time period set on the Razorpay dashboard will not be used for payments processed via payment providers other than Razorpay. Such payments will be auto captured by default.

      This is important to reflect the correct information as downstream payment providers will mark the payment as successfull and will settle to your account as per the settlement schedule even if Optimizer will wait for you to capture the payment manually.

    3. Configure Payment Capture Settings Using Orders API Capture values passed in the Orders API take precedence over the Payment Capture settings configured on the Razorpay Dashboard. You can use this to change the capture settings for individual payments.

      Remove this section too

    4. Let us say you want to: Auto-capture payments that are authorized within 2 days from creation. Manually capture payments that are authorized within 3 days from creation. Capture SettingsSelect Automatic Capture Automatic capture timeout = 2 days.Manual capture timeout = 3 days.Payments auto-refunded ifPayments not captured by you within 2 days. Payments are authorized after 3 days. Watch this video to see how to set up the Automatic and Manual Capture with Timeout option. To configure capture settings: Log in to your Dashboard. Navigate to the Account & Settings → Capture and refund settings (under Payments and refunds section). Click Change next to Automatic Capture. Under Automatic Capture, click the drop-down and select the time period in the Capture all payments authorised within field. For example, 2 days. Click Next. Select Capture manually via dashboard or API. Click the drop-down and select the time period in the Capture payments manually authorised within field. For example, 3 days. Click Next. Click Normal Speed and Save.

      Remove this entirely

    5. manually capture payments that are authorized after that time period.

      Remove this line and change this to

      auto refund the payments that are authorised after that time period

    6. Payment Capture settings are applicable only for payments created using the Orders API. For Direct Settlement merchants, payments will be auto-captured even if they are created without using the Orders API.

      Remove both the points

    7. You must ensure that all payments in the authorized state are moved to captured state within 5 days of creation. This is mandatory because payments that are not captured within this time period will be refunded automatically to customers.

      System ensures that all payments in the authorized state are moved to captured state within 5 days of creation. This is mandatory because payments that are not captured within this time period will be refunded automatically to customers.

    8. Specific business use case Some businesses such as those in the Ecommerce industry, may retain the payment in the authorized state and later move them to the captured state.

      Remove this point completely

    1. Let us assume you want to set up a custom rule wherein you want to route all payments coming from a particular referrer code (custom identifier) to a particular payment gateway (for example, Paytm).

      Route all payments coming from a particular referrer code to a particular payment gateway like Paytm using custom identifier.

    2. • Channels (Website, Android, iOS) • Payment Method (Card, Netbanking, UPI Intent and UPI Collect) • BIN Number (Card IIN Number) • Card Type (Debit, Credit, Prepaid, Corporate) • Card Brand (American Express, Diners Club, Discover and so on) • Card Issuer (SBIN, HDFC, ICIC, UTIB, KKBK) • Banks (SBIN, HDFC, ICIC, UTIB) • Amount (In Paise)

      Better spacing between bullet points

      And amount is in Rs

      For Card issuer and Banks write , so on in list of banks and issuers

    3. Let us assume you want to set up a custom rule wherein: Priority LevelsTransaction Split - Payment Gateway/ProviderPriority 1• 70% of transactions to be routed via Paytm • 30% of transactions to be routed via RazorpayPriority 2• 100% of transactions to be routed via PineLabs This means that if the transaction attempted through Paytm and Razorpay fails in Priority 1, then as per Priority 2, the transaction will be re-attempted through PineLabs. Watch this video to see how to perform method-based routing.

      Same here without priority

    4. Example 1 Let us assume you want to set up a custom rule wherein: Priority LevelsTransaction Split - Payment Gateway/ProviderPriority 1• 80% of transactions to be routed via Paytm • 20% of transactions to be routed via PayUPriority 2• 100% of transactions to be routed via Razorpay This means that if the transaction attempted through Paytm and PayU fails in Priority 1, then as per Priority 2, the transaction will be re-attempted through Razorpay. Watch this video to see how to perform channel-based routing.

      Told you not to have priorities.

      Put some sample example without priority in both table and gif

    5. In addition, fallback priority levels can be configured. This means that if a transaction assigned as Priority 1 fails, a secondary fallback Priority 2 can be established to ensure the transaction is redirected appropriately. This provides a level of redundancy and flexibility in the routing process.

      Remove this

      Add this new heading after payment parameters, above smart routing

      Custom Identifiers

      Apart from regular payment parameters, you might need to route payments to a particular gateway basis some business logic defined at your end like customer or product information. You can use custom identifiers for such requirements to pass the value to us while creating order and use it to create custom rule

      Add one example

    6. You can create a set of customised rules for your transactions on the basis of various parameters.

      Custom rules provides you the capability and flexibility to define your business rules using various payment parameters.

      Shift the example before the Supported Payment Parameters

    7. All your paymnets will have a standard rule set by default. You can edit this rule as per your business requirement. With Standard Routing you can: Set basic priority for all your payments. Prioritise the gateways for all your transactions. You can set the basic priorities and manage the payment gateways by using the Default Rule. This default rule acts as a backup plan, ensuring that all transactions have a path for processing even if they do not meet the criteria specified in any of the rules.

      You might not have special routing needs for all your payments. A very simple routing rule could be to set the gateway priority which will work for all the payments. This can be accomplished using the default rule.

      With Standard Routing you can: * Prioritise the gateways for all your transactions. * Distribute load among the gateways like 50% to payment A and rest 50% to payment gateway B.

    1. Banks like Axis, ICICI, HDFC, and so on, which provide their own payment gateway accounts to accept payments. While aggregators work with banks and provide you with the ability to accept a wide range of payments.

      Banks like Axis, ICICI, HDFC, and so on provide their own payment gateway accounts. While aggregators work with banks and provide a wide range of payments methods.

    2. You can add Payment Providers on the Razorpay Dashboard by submitting details through a self-serve flow.

      There are two kinds of payment service providers - Bank Gateways and Aggregators. Banks like Axis, ICICI, HDFC, etc which provide their own PG accounts to accept payments. While Aggregators work with Banks and provide you with the ability to accept wide range of payments. We support a range of bank gateways and payment providers

      You can add Payment Providers by adding few details on the Razorpay Dashboard. Every provider has a different set of prerequisites and details. Before adding provider, you will have to ensure that the PG/Aggregator is ready and has completed all the pre-requisites.

      Watch this video to see how to add Cashfree as a provider

      Add steps below the video like this https://razorpay.com/docs/payments/payment-links/create/

    3. This is a secure process, where access is restricted and the details are not shared internally for any purpose other than supporting your integration. Know more about Razorpay Security.

      This is not required

    1. Razorpay Optimizer allows you to set up customized rules for routing transactions through multiple payment gateways. These rules can be configured based on the specific requirements of your business. Additionally, Razorpay Optimizer allows you to dynamically route transactions using various available parameters, ensuring that transactions are processed through the most appropriate payment gateway based on various factors such as payment method, amount, issuer, and more.

      Create your rules on Razorpay dashboard to dynamically route transactions using different parameters like payment method, amount, issuer, and more. You can also add the priorities in every rule to ensure transaction is routed to the best performing gateway

    2. This process is secure, as access is limited and your information is not shared internally for anything other than assisting with your integration.

      This process is secure, and the details added by you are fully encrypted which is available on on your dashboard.

  3. betasite.razorpay.com betasite.razorpay.com
    1. Partial payments Allow your customers to make partial payments. You can also decide the first installment amount to be paid by customers in case of partial payments.

      Remove this!! Some copy paste

    2. Advantages
      • Ease Integration Optimizer is available on the fly with your existing Razorpay integration making it simple for businesses to start optimizing their payment transactions.

      • Real time Optimization Razorpay Optimizer uses real-time data to optimize payment routing, ensuring that transactions are routed to the best available acquirer or gateway.

      • Improved Success Rate By using real-time data, Razorpay Optimizer helps to reduce the number of failed transactions and improve Success rate.

      • Better Customer Experience Optimizer seamlessly routes the transaction to the bext performing gateway entirely through the backend without any customer intervention.

      Merging multiple points.

    3. Optimize success rates and cost. Distribute traffic across payment providers. Add payment providers within rule priorities as fallback.
      • Configure new payment gateways in just few clicks (No coding required)
      • Optimize your transaction costs using rules
      • Seamlessly optimize success rate with priorities and smart router
      • Access all your payments, refunds and settlements at one place
    4. You can create different rules based on payment methods, channels, card IIN number, card type, card brand, card issuer, banks and transaction amount.

      You can create different rules based on various parameters like payment methods, channels, card IIN number, card type, card brand, card issuer, banks, transaction amount and so on.

    5. You can also set up rules to route the transactions to them using various parameters like method, amount, issuer and so on.

      You can set up your own rules to route the transactions to different payment gateways. With every rule, you can also add your gateway priority which will be used if the higher priority gateway is facing any downtime/service degradation

  4. Feb 2023
  5. betasite.razorpay.com betasite.razorpay.com
  6. Nov 2022
  7. betasite.razorpay.com betasite.razorpay.com
    1. n the Cashfree Dashboard, select the old version for webhook responses.

      On the Cashfree Dashboard, select the v0 version for payment success, pending and fail state events.

    1. Know how to save customer card details as tokens on Optimizer using Razorpay's TokenHQ solution.

      Know how to save customer card details as tokens with multiple payment partners using Optimizer.

    2. Watch Out! If a merchant is a Token Requestor(TR) and tries to process a payment through PayU, the payment will not be processed. To enable this, please contact us at payments_optimizer@razorpay.com.

      If a merchant requests a token from payment partner other than Razorpay and tries to process the payment via other payment partner, please get in touch with us at … We’ll help you with the extra token attributes required by the payment partner to process the payment.

    3. If a merchant is a Token Requestor(TR) and tries to process a payment through PayU, the payment will not be processed. To enable this, please contact us at

      If a merchant is a Token Requestor(TR) and token is generated from payment partners other than Razorpay and tries to process a payment through payment partners other than Razorpay, please contact us at ... We might need few extra token attributed required to process payment through other payment partners.

    4. Razorpay offers an end-to-end RBI-compliant solution that allows you to save customer credentials as tokens with card networks and card-issuing banks

      Razorpay Optimizer offers an end-to-end RBI-compliant solution that allows you to save customer credentials as tokens with card networks and issuing banks and process payments through any PA/PG.

    5. Given below are a few examples of Optimizer Tokenisation flow when Razorpay is the Token Requestor.

      Given below is the Optimizer Tokenisation flow when Razorpay is the Token Requestor.

    6. You can use Optimizer and process payments on Razorpay and external gateways

      You can use Optimizer with Razorpay as Token Requestor and process payments on Razorpay and external gateways

    7. If you have enabled Tokenisation for Optimizer, you must redirect cards traffic to the supported payment gateways only. Know more about supported payment gateways.

      If you are using save card feature, you must redirect cards traffic to the supported gateways only. Know more about supported payment gateways

    8. With this solution, you can: Process payments through any PA/PG while tokenising cards through Razorpay. Use Razorpay Optimizer to route payments through the PA/PG of your choice.

      Remove this. Added this context above

  8. betasite.razorpay.com betasite.razorpay.com
    1. Analyse the contribution of each payment gateway or provider to overall payments. View the payment volume distribution with the help of a pie diagram

      What is the difference between these two statements?

    2. View the graphical presentation of all the payment providers for Cards transactions by selecting the individual payment provider label or overall label as per your requirement.

      Change this as per above suggestion

    3. View the payment method level breakdown of the payment volume distribution with the help of a pie diagram.

      breakdown and distribution cannot come together

      View the payment volume distribution at method level with the pie chart.

    4. You can also view the above information in graphical representation.

      The line graph show the SR distribution on Hourly, daily, weekly on Monthly basis as per your date range selection.

  9. Oct 2022
    1. success rate breakup

      This is not SR breakup. This is payment volume distribution wrt methods (when all method tile is selected) and gateways (when method tile is selected)

  10. Aug 2022
  11. betasite.razorpay.com betasite.razorpay.com
    1. If you want your unique identifier (Order ID) to be visible on PayU's dashboard, write to your PayU Relationship Manager asking to make the specific column (the one having your Order Id) visible on the dashboard. Know more about how to send your order id to Payu.

      To pass your unique Order ID or Receipt for every order, write to your relationship manager to show the 'xyz' parameter in PayU Dashboard and customize report. Know more about how to send your Order ID to PayU

    2. same value to PayU

      in 'xyz' parameter

      Add which parameter we are using to send the receipt value

      Razorpay passes this value to PayU in 'xyz' parameter

      (Parameter name should be available in jira ticket

      Next point Write to your PayU Relationship Manager to show this parameter (xyz) in dashboard and reports as per your use case (usage)

    3. A unique order id is generated whenever a payment is processed via Optimizer. This order id will not be visible on the PayU's dashboard as it is specific only to the merchant. You can pass your Order Id to PayU using Razorpay's Orders API.

      You might be generating a unique Order ID or Receipt for every order which can be passed to PayU via Orders API (with a link).

  12. Jun 2021
  13. betasite.razorpay.com betasite.razorpay.com
    1. These credits are available only for specific business categories to help them meet regulatory requirements.

      Credits are available for all. But generally useful for such business categories

  14. Sep 2020
    1. orders

      Add this for Go. You'll have to do the indentation. And for all the languages have provided the import statements. Add a line gap between the import statement and next code.

      import ( razorpay "github.com/razorpay/razorpay-go" )

      client := razorpay.NewClient("<YOUR_API_KEY>", "<YOUR_API_SECRET>")

      data := map[string]interface{}{ "amount": 1234, "currency": "INR", "receipt": "some_receipt_id", "payment": map[string]interface{}{ "capture": "automatic", "capture_options": map[string]interface{}{ "automatic_expiry_period": 12, "manual_expiry_period": 7200, "refund_speed" "optimum'

      } } }

      body, err := client.Order.Create(data)

    2. n this case, Razorpay polls the APIs intermittently to check the status. Once the bank confirms it to be successful, the payment attains authorized state.

      In this case, Razorpay polls the Bank APIs intermittently for 5 days to check the status. If we receive the payment status from the bank as Successful, the payment moves to the authorized state.

      Same as other link

    1. override

      The options sent in the below API take precedence over the account level auto-capture settings configured using the Dashboard.

      Can we change this statement to avoid using override. And use something like this. This is from in API doc

    2. Once a payment is created, you can auto-capture payments that are authorized within a certain time period and manually capture payments within a time period beyond that.

      Once the payment is created, you can auto-capture payments that are authorized within a certain time and beyond that manually capture payments within a set time.

      Right now, beyond that positioning is giving a feel of something after manually capture. What do you think?

    3. Payments are auto-refunded if ● Payments are not captured by you within 3 days.● Payments are authorized after 3 days.

      Here "are" is repeating both sides. It could be (also aligning with above one),

      Auto-refunded payments - Payments authorized after 3 days / Payments not captured by you within 3 days

    4. Payments are auto-refunded if Payments authorized after 2 days are auto-refunded.

      Auto refunded is repeating here in both sections

      It could be something like this,

      Auto-refunded payments - Payments authorized after 2 days

    5. In this case, Razorpay polls the APIs intermittently to check the status. If the bank confirms payment success, the payment is moved to authorized state.

      In this case, Razorpay polls the Bank APIs intermittently for 5 days to check the status. If we receive the payment status from the bank as Successful, the payment moves to the authorized state.

    6. Allows you to define custom auto-capture and manual capture timeouts. ● Minimum value is 12 minutes. ● Maximum value (default) is 5 days. Manual capture timeouts Allows you to define custom auto-capture and manual capture timeouts.● Minimum value is 12 minutes.● Maximum value (default) is 5 days

      Description in these two sections is exactly same.

      and if manual capture timeouts is representing the third option(Manually capture with set timeouts) then there is no need to mention auto capture in this section.

      Have a look and make changes accordingly.

    7. Once the bank confirms it to be successful, the payment attains authorized state. Learn more about late authorization.

      This does not look correct. (Bank confirm it to be successful) And attains is difficult word

      It could be, payment is moved to authorized state. Some simple statement