Your Razorpay account id.
Your Razorpay account id to which access token was generated.
Your Razorpay account id.
Your Razorpay account id to which access token was generated.
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
sub-merchant account status webhooks.
Its taking to 404 page
API key
This link is not working
Subscribe to webhook events to receive real-time notifications about the merchant account activation status.
Remove this line.
You can retrieve a merchant's account onboarding status
You can subscribe to webhook events to receive real-time notifications about the merchant account activation status.
Check your
Track your
Ensure that you enter the refresh token.
Ensure that you have passed the refresh token in the request.
Error
Are these existing message descriptions or are we adding new ones?
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."
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.
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.
A production client is using test mode
should we say test mode credentials?
Provide the client_id .
Can we say something like provide your application client id?
A server error occurred while serving this error.
Is this new or it is an existing error description? This sounds more like a internal server error.
Error
Is this error description?
4
We can just say Subscribe to Authorization Revoke Webhook. Dont mention event,
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.
acc_BFQ7uQEaa7j2z7
use this account id, it is mentioned in the get access token response.
acc_Dhk2qDbmu6FwZH
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]
Subscribe to Account Access Revoke Webhook Event (Optional)
Subscribe to authorization revoked webhook.
Subscribe to Account Access Revoke Webhook Event
account.activated_kyc_pendingSample Payloadaccount.funds_holdSample Payloadaccount.funds_unholdSample Payloadaccount.activated_kyc_pendingSample Payloadaccount.instantly_activatedSample Payloadaccount.payments_enabledSample Payload
Lets remove these.
BouVWhEiuKOvfc
Should we mention, where they can find the partner id?
platform/account
should this be platform or account? Lets not mention both.
flow
Should we instead say experience?
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.
Orders
Orders will be part of Payment Gateway product right? Please refer to the documentation here. https://betasite.razorpay.com/docs/razorpay/oauth-api-sample-codes/partners/aggregators/partner-auth
We need to have similar structure here too. We need to list products and how to use them, order is not a product it comes under PG
Recurring Payments for Partners
All example are for Partner Auth for payment methods. This could will added under Partner auth overview after subscriptions https://razorpay.com/docs/partners/aggregators/partner-auth
We will have to add this to OAuth as well.
Recurring Payments for Partners
Please refer to this documentation. https://razorpay.com/docs/payments/recurring-payments
For each payment method they have support banks information, we should link in these sections as well.
Using a Registration Link
Should we explain what is a registration link?
Create an Authorization
Link the API here
Create an Order
Same here. lets link the create order API
Create a Custome
Do we have an API for this? If so can we link it here.
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.
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
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
Dashboard
Have we checked this? Can a partner fetch the tokens of their sub-merchant customers on the dashboard?
Orders AP
Link to orders APIs
1.1 Using Razorpay
Same here, should we just say Using APIs?
Razorpay
Should this just be APIs?
Given below is a diagram which explains the different states the account moves to during its lifecycle:
lets say standard onboarding in the diagram too.
normal
We can replace all normal with standard onboarding.
With this feature:
We can remove this line.
If they breach this limit, the status changes to needs_clarification, based on the details previously submitted.
We can remove this line.
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.
The sub-merchant needs to submit the relevant details.
The sub-merchants need to submit rest of the KYC documents for verification.
PG Product Status
We can remove PG section. and also check any reference to PG in the document we can remove those as well.
Alerts and Webhooks🔗
Because we are adding another section for alerts and changing the title for 6. we can remove this title.
Alerts
We need to explain about alerts and what limits they are triggered. We can add other another section for alters.
6. Subscribe to Webhooks
We can just say web hooks.
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.
webhook events relevant to partners to
relavant webhook events to
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.
through the normal flow using the Onboarding APIs.
and will go through normal onboarding flow.
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.
(if GST is verified: ₹5,00,000; if GST not present: ₹50,000)
We can remove this gmv limits here.
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.
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)
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.
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.
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
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
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:
sub-merchants
We need to use the same terminology at all the places, sub-merchants/customers/sellers. above we are saying sellers.
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.
Disburse the payments using our Transfers APIs.
Control settlements and disburse payments using our Transfer APIs
Have complete control over settlements using Settlements APIs.
This is incorrect. we can remove this line.
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.
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.
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.
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.
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.
Marketplace
This we can remove to Route for now
```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
Fetch Transfers for a Settlement
for all settlements related APIs we can create a new page.
Refund Payments and Reverse Transfer from a Linked Account🔗
We can create a new page for Refunds & Transfer.
Transfers🔗
We can create a new page for this section.
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*?
Modify Settlement Hold for Transfers
Move this after Fetch a Transfer by ID section
fails
Can we link to a doc which has reasons for failures?
order
Add a doc link which explains about orders.
captured
Add a doc link which explains about payment capture.
aand
and