84 Matching Annotations
  1. Oct 2023
    1. string Identifies the sub-merchant id that granted the authorisation.

      This is not sub-merchant ID, as partner is using these APIs for creating sub-merchant accounts. It will be partner id here.

      We can just say Razorpay account id

  2. Jul 2023
  3. Jun 2023
    1. The authorization_code does not contain the correct redirect_uri

      Why are we talking about authorization code here?

      It should be on the lines "the redirect uri passed in the request is incorrect."

    2. Ensure that the authorization_code contains the correct redirect_uri .

      Ensure that the redirect_uri specified as same as the one added in the application settings.

    3. The authorization_code is not provided.

      is this error specific to only authorization code or can occur if other required params are not passed? If so then we should mention all the required params.

  4. May 2023
    1. We recommend subscribing to the account.app.authorization_revoked webhook event. This ensures that you receive real-time notifications whenever a sub-merchant revokes access to your connected application

      Add this as next para.

    2. Sub-merchants can revoke access to your application using the Razorpay Dashboard at any time. This can cause user experience issues. We recommend you to subscribe to the webhook event - account.app.authorization_revoked to receive notification when a sub-merchant revokes access to a connected application.

      Sub-merchants can revoke access to your application from their Razorpay Dashboard at any time. Once revoked, your application will no longer have the capability to perform any operations on the sub-merchant account. We recommend subscribing to the 'account.app.authorization_revoked' webhook, this will ensure that you receive real-time notifications whenever a sub-merchant revokes access to your connected application.

      Please follow the steps here on how to subscribe to webhooks. [Add link to subscribe to webhooks for here]

    1. account.activated_kyc_pendingSample Payloadaccount.funds_holdSample Payloadaccount.funds_unholdSample Payloadaccount.activated_kyc_pendingSample Payloadaccount.instantly_activatedSample Payloadaccount.payments_enabledSample Payload

      Lets remove these.

  5. Jan 2023
    1. Payment Gateway

      Support products, will be same as what we show for Partner Auth

      PG, PL, QR codes, smart collect & subscription. We will add recurring payments for both partner auth & oAuth.

      Orders, payments & refunds can be under payment gateway.

    1. 1. Create Authorisation TransactionCreate an authorisation transaction for UPI with TPV using Razorpay APIs.You can create an authorisation transaction using: Razorpay APIs Registration Link 1.1 Razorpay APIs 1.1.1. Create a Customer Razorpay links recurring tokens to customers via a unique identifier. You can generate this identifier using the Customer API. You can create customers with basic information such as email and contact and use them for various Razorpay offerings. The following endpoint creates a customer.

      All of this is same as above UPI section. We should some information on what is TPV explain the customer its use case.

    1. A registration link should always have an order amount (in paise) the customer will be charged when making the authorisation payment. This amount should be ₹1 in the case of UPI.

      This should be high lighted. Watch out box

    1. For UPI, it may take between 24-36 hours for the subsequent payment to reflect on your Dashboard. This is because of the failure of pre-debit notification and/or any retries that we attempt for the payment. Do not create another subsequent payment until you get the status of the previous one. For UPI, do not create subsequent payments on the last day of the cycle. This will cause the payment to fail.

      We should add this in a warning box or like a watch out section

  6. Nov 2022
    1. Razorpay reviews the details and releases the funds if everything is found to be in order.

      Razorpay team manually reviews the details submitted and fully activates the account after success verification. Payments and settlements will be enabled without any limits.

    2. You can use the Webhooks APIs to receive event notifications or subscribe to events happening in a sub-merchant's account, such as payments, orders, invoices and so on.

      This section can be moved to the end.

    3. However, they are all optional. They are provided for the partner to proactively collect documents before the product activation status changes to under_review.

      We don't have this implemented as of now. Can remove this line.

    4. If they breach this limit, the status changes to under_review or needs_clarification, based on the details previously submitted.

      With the current implementation, the status changes to only needs_clarifications.

    5. Business Email, Business Type, Business Category, Business Sub-Category, Business Name, Stakeholder Name, Stakeholder Email, Contact Mobile, Business Registered Address

      If required for other details we can create another column and list it there. It is not very readable now.

    6. Business Email, Business Type, Business Category, Business Sub-Category, Business Name, Stakeholder Name, Stakeholder Email, Contact Mobile, Business Registered Address, Owner PAN / Signatory PAN, Bank Account (IFSC Code, A/C No., Beneficiary Name), Business PAN (Optional), GST (Mandatory only if account is in 'Needs Clarification' state.)

      Personal PAN, Bank Account details (IFSC Code, A/C No., Beneficiary Name)

    7. Sign in to your Partner Dashboard to obtain your client_id and client_secret to authenticate API calls. You can obtain client_id and client_secret depending on the test mode or live mode.

      We want to say 1. sign up as Partner 2. Complete KYC to activated your account 3. To authenticate APIs calls you will require client_id and client_secret. 4. You can obtain client_id and client_secret for both test mode or live mode.

    8. The sub-merchants will need to submit documents only after they breach a specific transaction volume limit (if GST is verified: ₹5,00,000; if GST not present: ₹50,000). The funds will be on hold till the documents are submitted.

      Lets list the documents required for approval here. Add it in bullet points.

      Limits can be mentioned in another line.

    1. vendors and others.

      Lets add a warning box or another paragraph below this and say its a beta feature and list down the capabilities. This feature is in Beta. Feature capabilities, * Onboard your customers on to Razorpay to accept payments * Onboard your customers, third party vendors, other service providers including your bank account as Linked accounts to route funds into multiple accounts * Accept payments on behalf of your customers * Create transfers to split funds * Control settlements by holding the transfers until service fulfilment or as per agreement with your stakeholders. * Refund payments

    2. Razorpay Route is a product that enables you as a partner to split payments received using the Razorpay Payment Gateway or other products and transfer the funds to sellers, third-party logistics service providers, vendors and others.

      We can remove you as a partner from this line.

      Razorpay Route enables you to split payments received using the

    3. Given below is a diagram that briefly explains how Razorpay simplifies the payment split process, when handling multiple parties:

      Here lets marketplace reference in the sentence because not all partners are marketplace owner.

      Given below is a diagram that briefly explains how Razorpay simplifies the payment split process for marketplaces, when handling multiple parties:

    4. Use our Linked Account APIs to create linked accounts for sellers, yourself and the third-party logistics service provider.

      Before this we need to mention they have to create merchant/seller account to accept payments using accounts API.

    5. Please raise a request with our Support team to get this feature activated on your Razorpay account.

      Just ask you Sales POC or please raise a request with our Support team to get this feature activated on your Razorpay account.

    6. As a partner, you can enable sellers to onboard as linked accounts, accept customer payments using Razorpay product suite and disburse payments using Route.

      Control fund flow and split funds into multiple accounts.

    7. Marketplace Model - Onboard Sellers as Linked Accounts and Disburse Funds Using Razorpay Route

      I think we can keep it back as Route for Partners. This title seams to long.

    1. The following endpoint creates a Linked Account.

      Add a warning below this.

      This is a beta API. You will be requested to change your integration later to add live API.

    2. Linked Account Entity🔗

      Can you verify this. Are you sure the beta linked account API has so many fields?

      For linked account we don't collect or store all these details.

  7. Oct 2022
    1. ```curl: Curl curl -u [CLIENT_ID]:[CLIENT_SECRET] -X POST https://api.razorpay.com/v1/subscriptions/sub_00000000000001 \ -H "Content-Type: application/json" -H "X-Razorpay-Account: acc_Ef7ArAsdU5t0XL"

      Move this to next line or add in a code block

    1. You can use the following endpoint to modify the settlement configuration for a particular transfer_id. On a successful request, the API responds with the modified transfer entity.

      Can we explain why we need to do this or the use case. We can say something like * to release transfers on hold for settlement you can modify a particular transfer*?