3,788 Matching Annotations
  1. Dec 2022
    1. s passed.

      This error occurs when the time mentioned in the expire_by parameter has already passed. For example, if today's date is 12 December 2022, however, the expiry date is mentioned as 10 December 2022

    1. You can use Razorpay webhooks to configure and receive notifications when a specific event occurs. When one of these events is triggered, we send an HTTP POST payload in JSON to the webhook's configured URL. Know how to set up webhooks.

      We can remove this since webhook doc is already linked in the first few lines.

    1. account

      fund account or Fund account or Fund Account.

      All three variants have been used. Could you please check what is the standard for X Docs and ensure that spelling is used throughout the docs?

    2. Overview of Account Validation for RazorpayX, APIs and webhook payload. Validate a customer's bank account before you make payouts.

      Overview of Account Validation for RazorpayX. Use our APIs to validate a customer's bank account before you make payouts. Receive webhook notifications on the account validation status.

    1. After completing the integration, Razorpay will appear as a payment option on your web page/app. You need to click the button and make a test transaction to ensure that the integration works as expected. You can start accepting actual payments from your customers and transfer them to Linked Accounts once the test is successful.

      After completing the integration, you can simulate a test payment transfer. After the test is successful you can start accepting real-time payments and start transferring them to linked accounts.

    1. The Debit Card EMI payment method is not allowed for the Subcategories for which the Status field is N in the file

      The Debit Card EMI payment method is not allowed for certain business categories. Refer to the status column of the categories file. Debit Card EMI is not allowed for categories with Status is marked N.

    1. Raise a request using the Razorpay Dashboard for any issues regarding Cash Advance or Working Capital Loans and the RazorpayX Dashboard for Add-on Cards.

      Can we split this into two points please?

      At the moment this line has a lot of hyperlinks and I am confused on what to click.

      Suggestion: (Link only the Dashboards perhaps) For any issues regarding: - Cash Advances and Working Capital Loans: Raise a request on the Razorpay Dashboard. - Add-on Cards: Raise a request on the RazorpayX Dashboard.

    1. The customer can select the Save card securely for future payments options.

      we need to merge points 3 and 4

      1. While making a card payment, the customer can choose to save or not save their card details for future transactions, with card networks (such as Visa, Mastercard) or card issuers.
      2. To save card details: The customer should select the Save card securely for future payments option, and proceed with the payment.
      3. To not save card details: The customer should not select the Save card securely for future payments option. Also, they should click Pay without Saving Card and complete the payment.
    1. is the per

      since it is a rank, I assume it to be like 1,2,3 and not in percentages... I may be wrong as there is no UI to check.

      Can you please check the spec doc and see if there is more info on how this is calculated?

    1. With Razorpay, you can use MOTO (Mail-Order-Telephone-Order) transactions to charge a customer's credit card without CVV or 2-factor authentication.

      With the MOTO (Mail-Order-Telephone-Order) payment method, you can charge a customer's credit card without CVV or 2-factor authentication.

  2. Nov 2022
    1. Thirdwatch has not had significant feature development in the recent past. As the requirements have evolved over the years, we have decided to sunset Thirdwatch to focus on providing better features. Razorpay has launched a smarter, better & more robust solution to help you reduce RTOs in the form of Razorpay Magic Checkout. Besides providing everything Thirdwatch offered, Magic Checkout has a lot more to offer!

      Thirdwatch has not had significant feature development in the recent past. As the requirements have evolved over the years and we built newer products, we have decided to sunset Thirdwatch and merge its capabilities with Magic Checkout - a smarter, better and more robust solution to help you reduce RTOs.

      Besides providing everything Thirdwatch offered, Magic Checkout has a lot more to offer. Know about Magic Checkout's advantages and discover how it can suit your business use case.

    2. We launched Thirdwatch in 2019, an AI-driven solution from Razorpay that helps online sellers prevent Return to Origin (RTO). It analyses customer orders based on various parameters and flags risky orders in real-time. It allows you to make Go or No-Go decisions on these orders, preventing RTO losses to your business. While the goal is to flag suspicious orders and prevent RTO, we have decided to deprecate Thirdwatch to further our commitment to enhancing the checkout experience, reducing RTOs and more via Magic Checkout.

      Suggestion:

      We launched Thirdwatch in 2019, an AI-driven solution from Razorpay that helped online sellers prevent Return to Origin (RTO). It analysed customer orders based on various parameters and flagged risky orders in real time. Based on this analysis, Thirdwatch allowed businesses to make Go or No-Go decisions on these orders, thus preventing RTO losses.

      In 2021 we launched Magic Checkout, which combined an enhanced checkout experience with the risk and fraud analysis capabilities of Thirdwatch.

      As Magic Checkout has become stable and robust, we have decided to deprecate Thirdwatch.

    3. Deprecating Thirdwatch on 31 Dec 2022 to enhance the checkout experience and prevent RTOs via Magic Checkout.

      We are sunsetting Thirdwatch on 31 Dec 2022 and recommend users to migrate to Magic Checkout.

    1. Now that an offer is created, you should integrate the offers with the Checkout for customers to avail themselves the discounts and make payments.

      After the offer is created, you should integrate it with Checkout so that customers can avail discounts while making payments.

    2. - Select the Starts Immediately check box for the offer to come into effect immediately. Expires On - Select the date and time at which the offer should end. For example, 31 Oct 2020 at 11:59pm. On Payment Failure - Define how to handle payment failure. Do not allow payment to go through: The payment is failed. Allow customer to pay without availing offer: The payment is allowed even though the set validations are not met. However, the offer is not applied to the bill amount. The customer will be charged the entire order amount. We will allow payments to go through without an offer being availed. Max Usage - Set the number of times the offer should be applied across all transactions. For example, 100. Show Offer on Checkout - Sel

      replace - with :

    3. - Enter the minimum bill amount for which the No Cost EMI offer can be applied. For example, a customer must purchase an article of at least ₹4000 to avail No Cost EMI. This is a mandatory field. Maximum Order amount -

      replace - with : and add commas in the amounts. for example, 3,00,000.

    4. Enter the name of the offer. For example, Diwali Dhamaka. Display Text - Enter a meaningful description for the offer. For example, No Cost EMI Offer. This appears at the Checkout. Terms -

      replace - with :

    1. The Unix timestamp, indicates from when the Subscription should start. If not passed, the Subscription starts immediately after the authorization payment.

      Unix timestamp that indicates from when the Subscription should start. If not passed, the Subscription starts immediately after the authorisation payment.

    2. The Unix timestamp, indicates from when the Subscription should start. If not passed, the Subscription starts immediately after the authorization payment

      Unix timestamp that indicates from when the Subscription should start. If not passed, the Subscription starts immediately after the authorisation payment.

    1. netbanking, wallets, UPI Collect, UPI Intent, Cardless EMI and Emandate sections to know about the possible values for each method.

      same here, let us remove the other payment method links

    2. The point of failure in the specific operation (payment in this case). Check the card, netbanking, wallets, UPI Collect, UPI Intent, Cardless EMI and Emandate sections to know about the possible values for each method.

      Check the card section to know about the source.

      Let us remove the other payment method links since they are not relevant here

  3. betasite.razorpay.com betasite.razorpay.com
    1. If you accept payments on your website or app using multiple payment gateways Razorpay Optimizer allows you to route transactions to all these gateways with one integration.

      If you accept payments on your website or app using multiple payment gateways, Razorpay Optimizer allows you to route transactions to all these gateways with one integration

    1. { "inquiry": "affordability", // new "amount": 100000, // mandatory "currency": "INR", // mandatory "customer": { "id": "cust_JbRkXMROZUMCVq", "contact": "+919000090000", // mandatory "alternate_contact": "9900099000", // new "imei": "6234672537253752735", // new "ip": "105.106.107.108", // new "referrer": "https://merchansite.com/example/paybill", // new "user_agent": "Mozilla/5.0", // new "addresses": [ // new { "name": "Gaurav Kumar", "line1": "SJR Cyber Laskar", "line2": "Hosur Rd", "landmark": "Adugodi", "zipcode": "560030", "city": "Bangalore", "state": "Karnataka", "contact": "9000090000", "tag": "office", "type": "shipping" }, { "name": "Gaurav Kumar", "line1": "Arena Building", "line2": "Hosur Rd", "landmark": "Adugodi", "zipcode": "560030", "city": "Bangalore", "state": "Karnataka", "contact": "9000090000", "tag": "home", "type": "billing" }, { "name": "Gaurav Kumar", "line1": "SJR Cyber Laskar", "line2": "Hosur Rd", "landmark": "Adugodi", "zipcode": "560030", "city": "Bangalore", "state": "Karnataka", "contact": "9000090000", "tag": "office", "type": "saved" } } }, { "instruments": [ { "method": "emi", "issuers": [ "HDFC" ], "types": [ "debit" ] }, { "method": "cardless_emi", "providers": [ "zestmoney", "walnut369" ] }, { "method": "paylater", "providers": [ "simpl", "lazypay" ] } ] }

      please update the sample code. I have fixed it and am sending on slack

    1. To do this, navigate to Reports → Ledger. XPayroll displays all compliance payments individually for all employees and contractors. If there are no entries here, XPayroll has not made any such deductions. Next, please check the Status column in your ledger report. If the status is Success then the payment has already been made. If it is Pending then the payment will happen soon.

      Can we make convert these into steps please?

      To do this: 1. Log into the XPayroll Dashboard(?!). 2. Navigate to Reports → Ledger. XPayroll displays all compliance payments individually for all employees and contractors. If there are no entries here, XPayroll has not made any such deductions. 3. Check the Status column in your ledger report. If the status is Success then the payment has already been made. If it is Pending then the payment will happen soon.