Lets call this "Track Onboarding Status"

This should be "Onboarding Webhooks"

Can we add the same 3 color image from overview here?

Can we make it point 5?

This should be documents entity. and Lets add the entity here

Same. Lets add Product entity definition here

Lets add the account entity here. Referencing to another page makes it difficult to read. If this makes the page too long, we can break the Onboarding SDK into mutiple pages

Lets add a statement after this

"Here are the APIs that are available for Onboarding customers"

Fetch access token associated with the merchant

Create account and upload KYC details using onboarding APIs

Can we make these hierarchial and add numbers? So the right nav is more cleaner?

Can we make these headings hierarchial?

Custom Onboarding SDK allows you to perform Razorpay signup and KYC steps through API. With this, you can collect details and documents within your UI instead of Razorpay hosted UI.

Can we move pre-requisites to the end? We are introducing two types of onboarding in previous statement. Ideally it should be followed by explaining those two types..

Can we add the 3 color image post this statement?

This is not in beta

Can we rename this "Co-branded Onboarding Settings"

Can we rename this section as "Standard Co-branded Onboarding"?

Lets not make this a call out. We already established this. Lets add a regular text that says we need to use auth token created in so and so step for accessing this API

You can pass platform and third party fees as a transfer while creating an order using Orders API

Lets remove this. Not relevant for Partners.

We need to fix this redirection to new page as well

Lets remove the placeholder for the image below

Can we adjust the size of this image? Right now it is too big to view in one screen

Lets have 3 sub-pages under this

1. Overview
2. Integrate with OAuth
3. Customise Onboarding

Can we move this into a new page?

The image below is not ready from design. For now lets go ahead without it

Image to be added here

Delete this

“Connect with Razorpay” CTA embedded

video above

lets remove this. We don't have demo yet. We gave GIF

https://razorpay.slack.com/archives/C3L0JR3FY/p1687249464207579?thread_ts=1685691571.024429&cid=C3L0JR3FY

Lets add the GIF here

Lets remove this

Example

On the left navigation in the title, can we remove (new)?

Sign-up as Razorpay Partner using steps here. Contact your sales POC to enable Platform Partnerships for your account

"Co-branded Onboarding UI" Lets make it bold

Lets break this into next para

Can we put this into next paragraph? This is one long para right now

Razorpay for Platforms and Marketplaces allows you to onboard businesses, process payments and control flow of funds all within your platform.

Offer end to end payments solution to businesses on your platform

Get Dashboard Access

Can we add the steps similar to you we did for platform section?

Download Platform Fee Reports

Can we call this Platform Fee reports?

Can we add this section as is in here? https://razorpay.com/docs/payments/dashboard/reports

This overview page is not needed. We can directly have three sections

I updated content for this section in doc. Please check

Lets remove this content

Lets add the content from here - https://razorpay.com/docs/payments/route/view-reports

Lets move this table under "Related Reports"

Can we add the content from here? https://razorpay.com/docs/payments/dashboard/reports#download-reports

Just the download reports section, not list of reports

Third-Party

Caps

Seller, or Third-Party Service Provider

Caps

Can we break these into separate pages?

Lets remove this section for now. We will add it after legal signoff

These are supposed to be separate pages. Lets use same navigation as in doc

Collect platform fee and third party charges from customers

I updated the req doc with code snippets. Please check and update here

Using the access token generated, you can view create payments, refunds, payment links or other entities on behalf of your sub-merchants.

Use our API reference guide <here> to see full list of all APIs available from Razorpay.

Here is a sample API request using OAuth Access Token

access tokens

YOUR ACCESS TOKEN

The webhook end-point must return a status code

Can we call this "Onboarding status webhooks"?

This entire section don't have any images or GIFs. Can we have a GIF for a sample phantom page with partner theme?

Configure the merchant onboarding theme as per your platform branding in your partner dashboard

I don't think this is relevant now. We should rather call it co-branded onboarding?

Can this be UI? Both capital

Can we add a screenshot?

they will receive the payout in next 7 days. not next month

I think there should be a comma here

Lets hide few characters of this referral link

Cn we hide the MID in all screenshots?

Lets replace You with "businesses"

This is a merchant facing feature, not partner facing feature. Can we make it more explicit?

This is not needed as a separate section. Just a tip that you can use test mode for testing webhooks is enough

Can we have screenshots for this section?

This is not required in go live checklist. This is an optional feature

I don't think this section is correct at the moment. Tokens do not have expiry as of now

Can we do this with a request and response code block that we user everywhere? A separate section is not needed for both. A simple code block with a section explaining all params is good enough

Same comment as before. Lets give these details in individual steps

Can we directly jump into the steps and explain these under individual step? User will not know these terms yet unless they see the flow.

Can we have the end to end integration in one page? This is a simple integration. I feel we should try and cut down the content to make it simple. To fit in one page..

Let's add another point before this where a user have to login if not logged already.

Once logged in they will be presented a Authorisation screen

Lets add a screenshot of authorise screen here

Application

"A front end interface for your app with a button to redirect the user to Razorpay OAuth page"

Top most pre-requisite, they need to have a platform partner account with Razorpay.

They can get the platform partner account created by reaching out to support

Is this needed?

Can we have a user flow diagram or a video that explains this rather than a paragraph? Basically the end the end flow for OAuth.. Or if we are doing it later, then lets make this example more structured with bullets maybe

Can we break this into more bullets. This is a very large paragraph

2nd point is not applicable now that makes the 3rd point vanity. Do we still need this advantages section?

As of today, the token don't have any expiry. We are planning to add but not available now.

account

Can you make this bold?

Can you make this Bold?

This reference is wrong. Not relevant to Integromat

to automate your workflows

How is this different from this? https://razorpay.com/docs/webhooks/validate-test/#order-of-webhooks

How is this different from this?

https://razorpay.com/docs/webhooks/validate-test/#idempotency

How is this different from this content? https://razorpay.com/docs/webhooks/setup-edit-payments/#deactivation

This should be in the Level 1 Navigation. Just like Set Up and Edit Webhooks.

What does priority mean?

We should first define what is a rule and limit.

The structure of the content doesn't look correct. Throttling Techniques, Rules and limits and Dashboard actions should be subsections under Throttling. If required we can make a separate section under platform called "Edge - Throttling"

These doesn't look like examples but more of an explanation. Can we some sample rules and explain if we want to have examples?

Can we make this H2 under Throttling?

This should be more prominent

The actual point of this section is that webhooks will not be delivered in the same order as they occur. We should highlight that.

Currently, that is not prominent here.

I don't think we need this paragraph.

We can start with -

There could be scenarios where your endpoint might receive same webhook event multiple times. This is expected as per design and can be handled easily using x-razorpay-event-id header

Check the value of x-razorpay-event-id in the webhook request header. The value for this header is unique per event You can cross reference on your end to identify if an event with same header is processed on your end already to avoid duplicates.

But why do Razorpay sends same event multiple times? To avoid an event being missed, Razorpay follows at-least-once delivery semantics. In this approach, if we do not receive a successful response from your server, we resend the Webhook.

There could be situations where your server accepts the event but fails to return a response in 5 seconds. In such cases, the session is marked timeout. It is assumed that the Webhook has not been processed and is sent again. Ensure your server is configured to handle or receive the same event details multiple times using the solution as mentioned above.

Lets add a reference to our Language SDKs here

Do we need this subheading?

Did we remove the note that says, signature generation should always use raw payload? https://razorpay.com/docs/webhooks/#validation

Lets call this "Next Steps"??

In next line -

You will receive webhook deactivation notifications to this address. Refer <webhook deactivation> for more details.

When a webhook gets disabled, Razorpay will send you an email notification on "alert email" as configured during set-up.

Lets say Click "+Add New Webhook" for better readability.

Can we give a reference to Validate webhooks here? May a one liner that says, if you configured a secret, here is how you can validate the signature on your end. <link>

Lets break this into two paragraphs. This looks like a very long paragraph

Lets give a reference to edit webhooks section

can we make these bold? Or some distinction, may be italic or underscore

Should be capital Letter

Can we make the questions bold?

APIs send you the data when you request for it. For Webhooks, you don't need to make a request. You receive the data when it is available.

This is common for both Razorpay payments/RazorpayX. Also the secret definition. Can we either add it both places or keep it outside individual sections?

These two tips should be moved after all code snippets.

Edit webhooks can be added after this as 6th point.

We should remove this and move the definition of secret here. The hyperlink is not taking to exact section.

Razorpay payments dashboard

This is a generic definition. Should be outside payments suite.

Also, 'Payments suite' is a not commonly used term afaik. May be we should call it payments dashboard?

I think this is only true for PG dashboard, X dashboard doesn't allow multuple webhooks at the moment

Lets call it 'Razorpay payments'

Do we call these videos? I think we use someother word for Gifs. Infographic?

I think these should not be under FAQ. These are generic definitions. FAQs should cover more Razorpay specific questions

We should have a frequently asked questions section at the end after sample payload.

Can we name it "When to use webhooks?"

We can keep use cases under this, but both Idempotency and Secret should be moved to Set-up and validate webhooks.

This section can be cut down to a 2-3 sentences with an line example.

"APIs send you the data when you request for it. For Webhooks, you don't need to make a request. You receive the data when it is available"

Ex: Imagine, you need to know if of a payment link is paid. With API, you will have keep polling every few seconds until someone pays. With Webhooks, you will receive the update when payment happens.

Too early to introduce this. This should be part of Webhook set-up.

This definition comes out of no where here. I think we should either skip it or add it to a separate glossary of keywords.

This can be combined with Set-up.

The flow for set-up and edit comes together functionality wise. Separate guide may not be necessary.

Right after set-up add a paragraph with screenshot that users can edit the webhooks whenever they want using 'edit option' '

These two as well. Lets make it "Testing against an application running on localhost" or something else which makes the heading complete..

Lets just call it "using request interceptor tools". The sentence looks broken.

I think some issue with hyperlink. Assuming this will be fixed in prod

Let's move this to Use Cases section. After 'Notifications on Failed payments' and before Idempotency

In most cases, webhook events will be delivered within few seconds of the associated event. However, in some cases this can be delayed by few minutes due to various reasons.

While we try to send them in a timely manner, we do not recommend relying on webhooks for events that are time-sensitive. For business-critical, synchronous use cases, please poll our APIs for the data.

On second thought, I think we can remove this table. The paragraph before this table is pretty self-explanatory and clear.

needs to be changed to 'this step will be skipped' - since this is not in user control. We skip it automatically.

Lets add 'You can get sample payload for all events <here>' with reference to sample payload

Lets add 'Learn more about Webhook secrets <here>' with reference to signature validation section

Let's just call it URL. It was wrong in old docs as well.