3,788 Matching Annotations
  1. Jun 2022
    1. Once you review the widget, integrate the widget on live theme. In the Current Theme section, click Edit Code under Actions and follow the same steps as given above.

      After you review the widget, integrate the widget with the live theme. In the Current Theme section, click Edit Code under Actions and follow the same steps.

    2. Fetch the class name of the product price element on the your website so that we can insert the widget html below and display the widget.

      You should fetch the class name of the product price element on your website. This is required to insert the widget HTML below and display the widget.

    3. Copy the JS File to theme.liquid and add it to the end of the theme.liquid file just above </body> and click Save.

      Copy the following code and add it to the end of the theme.liquid file, just above </body>. Click Save.

    4. The duplicate file will appear in Theme Library, click Actions and select Edit Code.

      The duplicate file appears in the Theme Library. Click Actions and select Edit code.

      Highlight Edit code in the screenshot

    5. Integrate the widget in the duplicate file so that in case of any unexpected error(s) the live store is not impacted. This is a mandatory step.

      Integrate the widget in the duplicate file to ensure that the live store is not affected in case of any unexpected error. This is a mandatory step.

    1. Delhivery is the largest and fastest-growing fully-integrated player in India by revenue that aims to build the operating system for commerce.

      Delhivery is an Indian supply chain and logistics company aiming to build an operating system for commerce. Integrate Magic Checkout with Delhivery to easily fetch delivery status details.

    1. and pass the payme

      There are two ways to pass the checkout parameters: using payloadhelper or the default JSONObject options. We recommend using payloadhelper as it ensures that the right data types are used for the parameter values.

  2. betasite.razorpay.com betasite.razorpay.com
  3. betasite.razorpay.com betasite.razorpay.com
  4. betasite.razorpay.com betasite.razorpay.com
    1. owing endpoint:

      think I made a mistake earlier. We need to have only one section. However, we will need two responses- one for Standard and one for UPI. This is because there is no difference in the request code for both PL variants.

    2. Payment Link:

      think I made a mistake earlier. We need to have only one section. However, we will need two responses- one for Standard and one for UPI. This is because there is no difference in the request code for both PL variants.

    3. lar Payment Link.

      I think I made a mistake earlier. We need to have only one section. However, we will need two responses- one for Standard and one for UPI. This is because there is no difference in the request code for both PL variants.

    1. The first 6 to 9 digits of the customer's card number depending on the network.

      Add these points as well

      The IIN length will be 6 digit for: - Non-tokenised card IINs for all networks - Tokenised IINs for Amex

      The IIN length will be 9 digit for tokenised IINs for Visa and Mastercard.

    2. According to the RBI Guidelines on Tokenisation, Payment Aggregators (PA)/ Payment Gateway (PG) and businesses cannot save their customers' card numbers and other card data on their servers. Only card networks can tokenise cards, which means you can save the card to tokenise the card. You can save the tokens and process subsequent payments via tokens.

      As per RBI guidelines, businesses or Payment Aggregators cannot save actual card numbers on their servers. They can only tokenise the card and use these tokens for subsequent payments.

  5. betasite.razorpay.com betasite.razorpay.com
  6. May 2022
    1. he API keys passed during checkout match the API keys used while creating the order_id/customer_id.

      The API keys passed during checkout should match the API keys used while creating the order_id/customer_id.

  7. betasite.razorpay.com betasite.razorpay.com
  8. betasite.razorpay.com betasite.razorpay.com
    1. Once the list is added, you cannot edit the items in the list. You can only delete each item in the list.

      Once added, you cannot edit the items in the list. You can only delete each item in the list.

    2. In the case of high-risk customers, you can create a blocklist. The customers mentioned in the blocklist based on the order phone number, email ID, device IP and shipping zip code will not be eligible for COD. You can create an allowlist in case of trusted customers. The customers mentioned in the allowlist based on the order phone number and email ID will be eligible for COD.

      bullet these.

      Maybe give an example of what is a high-risk customer? You can also try to add a use case section.

  9. betasite.razorpay.com betasite.razorpay.com
    1. In an online transaction using UPI collect flow, customers enter their virtual payment address (VPA) at the Checkout, open the respective UPI apps and complete the payment after successful two-factor authentication. Customers are redirected to your website or app after successful payment. In this flow, if the customers enter invalid VPAs or forget their VPAs, it may lead to higher drop-off rates. With Razorpay, you can save the VPAs of a customer at the Checkout itself. The VPAs entered by the customer are stored and secured as tokens in Razorpay. The customers do not need to enter the VPAs and use the saved VPAs every time they make a transaction.

      In an online transaction using UPI collect flow, customers perform these steps: 1. Enter their virtual payment address (VPA) at the Checkout. 2. Open the respective UPI apps. 3. Complete the payment after successful two-factor authentication.

      Customers are redirected to your website or app after successful payment. In this flow, if the customers enter invalid VPAs or forget their VPAs, it may lead to higher drop-off rates.

      With Razorpay, you can save the customer's VPAs at the Checkout and secure them as tokens in Razorpay. The customer does not need to enter the VPAs and can use the saved VPAs every time they make a transaction.

    1. Once the debug mode is activated, all the API logs and errors are collected and stored in your WooCommerce Dashboard. We recommend you to activate this feature.

      After the debug mode is activated, all the API logs and errors are collected and stored in your WooCommerce Dashboard. We recommend you to activate this feature.

    2. Magic Checkout does not support multiple shipping methods for a region. For example, if free shipping and flat rate shipping methods are enabled for a particular region then Magic Checkout will only consider free shipping as the shipping method.

      Magic Checkout does not support multiple shipping methods for a region. For example, if you have enabled free shipping and flat rate shipping methods for a particular region, then Magic Checkout will only consider free shipping as the shipping method.

  10. betasite.razorpay.com betasite.razorpay.com
    1. d below.

      Can we move out of a table into a section approach? Each user role can be a section with Action Allowed, Action Not Allowed as sub sections?

      Just thinking out loud. Also, we can do this in a different PR

    1. A payment gateway is an e-commerce service that accepts and processes digital payments for businesses.

      A payment gateway creates a secure pathway between a customer and the business to facilitate payments securely. It involves the authentication of both parties from the banks involved.

    1. Ad

      The screenshot seems a bit blurry to me. will we be replacing them later? Also, it contains qa.testing@razorpay.com. we should mask it so that security folks don't come point it out again

    2. Accept payments from customers on your website and mobile app using the Razorpay Payment Gateway.

      Should we say enables you to generate API keys instead? because this app helps you do that much only