If the partial reversal is done on transfer,
Same as above. Let's use amount for better understanding @palu
234 Matching Annotations
- Aug 2022
-
betasite.razorpay.com betasite.razorpay.comRoute12
-
-
complete
Don't think complete is right here. Let's use entire amount is reversed instead
-
You can initiate the reversal if required.
Why do we need this here? @palu
-
A unique identifier of the settlement
Language needs rework @palu Refer this for settlement ID description: https://betasite.razorpay.com/docs/razorpay/route-api-guide-revamp/api/settlements/
-
Indicates whether the account settlement for transfer is on hold.
Language needs rework @palu.
-
ype of the error.
Example? @palu
-
Error description.
Make it verbose @palu along with example
-
The stage where the transaction failure occurred. Stages can be different depending on the payment method used to make the transaction.
Add example please @palu
-
customer, business and so on.
How will this be populated @palu? Example?
-
The amount reversed from this transfer for refunds.
Not necessarily for refunds @palu. Just saying amount reversed for this transfer should be sufficient. Do make the necessary changes to make the description look complete
-
A unique identifier of the transfer destination, that is, the linked account.
Please rephrase this. @palu. Doesn't look right.
-
null (only in the case of Direct Transfers).
Not crystal clear. Will lead to confusion. @palu
-
-
betasite.razorpay.com betasite.razorpay.com
-
the same response as the first t
Sentence structuring isn't correct
-
that
which
-
quest with the Idempotency Key?🔗
same idempotency key
-
key is no
Idempotency key
-
n 4 (random) UUID
Give an example here
-
the reques
Create Direct transfer request
-
By default, t
Again, don't think comma is required here.
-
Currently, idempotency is supported on
Also, let's use idempotent request and not just idempotency please.
-
Currently, idempotency is su
comma isn't required here.
-
repeating the transfer request more than once.
let's not use this. let's try to sell this one like without having to worry about duplicate transfer being processed. You can use similar to what X has done
-
- Jul 2022
-
betasite.razorpay.com betasite.razorpay.comRoute7
-
ON THIS PAGE
This section and nesting doesn't seem to be correct. Can you relook at this? @palu
-
You can proceed to create a new transfer request.
As a note it makes sense to add that it will be retried for order transfers @palu
-
till the transfer is waiting to be processed.
Don't think the language is right here @palu
-
hich the record
What record?
-
"region": "south", "city": "Bangalore".
Have you checked this? @palu
-
he source can be a payment or an order.
What about direct transfer? Can you add about that too here? @palu
-
d in the following APIs.
Doesn't sit right as you are not listing the APIs here. Do check please @palu
-
-
betasite.razorpay.com betasite.razorpay.com
-
{ "status":"verification_pending", "beneficiary_name":"Madishetty Saketh", "account_number":"41390812314", "ifsc_code":"ADCC0000014" }
Add response for both penny testing enabled and not enabled. verification_pending when penny testing is enabled. activated when penny testing is not enabled. No other changes
-
Use the following endpoint to update bank account details
Bank account details for the linked account / whatever standard we follow
-
string The ifsc code of your bank account.
Webhook?
-
string Indicates the status of a Linked Account. Possible values: activated not_activated verification_failed (penny testing enabled) verification_pending (penny testing enabled)
These statuses aren't correct. We will only have activated, verification_pending, verification_failed. Also, should we put penny testing here? I think this section can be improved
-
Request Paramete
There should be path parameter as well, no? No description of what is :id. This is linked account ID. Please describe it whatever standard we follow
-