Webhook Payload
Webhook
Webhook Payload
Webhook
Given below is the sample payload for webhook events for Razorpay Optimizer. All the parameters and events will remain the same as shown in the sample payloads for payment webhooks except for one additional parameter, gateway_provider.
You can use Razorpay Webhooks to configure and receive notifications when a specific event occurs. When an event is triggered, we send an HTTP POST payload in JSON to the webhook's configured URL.
You can set up Webhooks from your Razorpay Dashboard
Sample payload for webhook events for Optimizer. All the parameters and events will remain the same as shown in the sample payloads for payment webhooks except for one additional parameter, gateway_provider.
Razorpay
remove this
payu_optimizer
payu
payu_optimizer
payu
Indicates the payment provider information.
The payment provider used to process the payment. Possible values: payu cashfree paytm pinelabs ccavenue ingenico billdesk_optimizer
payu_optimizer
payu
API Response
Payments API
Payments APIs are used to capture and fetch payments. Payment entity has one extra field with Optimizer to identify the payment provider through which payment is processed.
Know how to use the Razorpay Optimizer to write rules and route transactions through different payment providers.
Change this according to heading now
Given below are the supported payment providers and payment methods for Cards, Netbanking, UPI and Wallets.
Given below are the supported payment providers and payment methods for Cards, Netbanking, UPI, EMI and Wallets.
Razorpay Optimizer supports wallets for PayU, CCAvenue and Paytm. Know more about wallets supported by Razorpay.
Optimizer supports wallets for Razorpay, PayU, CCAvenue and Paytm. Know more about wallets supported by Razorpay.
some specific information
those details
information
remove this
Apart from the default rule, you can also create a set of custom rules for transactions. Also, you can set up priority levels. This means that if the success rate (SR) of a particular gateway assigned to Priority 1 drops below a certain level, all transactions will automatically be routed to the gateway assigned to Priority 2.
You can create a set of custom rules for transactions using different parameters like Payment method, Card Type, and so on, add gateways in priority order, split traffic between gateways.
• 20% of transactions to be routed via Paytm
Remove Paytm option. Using only one gateway on both priorities
Accordingly modify the gif
In addition to standard and dynamic rule-based routing, Optimizer allows you to assign priority levels to all your transactions. This means that if the success rate (SR) of a particular gateway assigned to Priority 1 drops below a certain level, all transactions will automatically be routed to the gateway assigned to Priority 2, creating a temporary downtime for the gateway assigned to Priority 1. This ensures that payment processing remains smooth and uninterrupted for your customers, even if some payment gateways are experiencing issues. Once the temporary downtime is automatically resolved, that is, when the SR of the gateway assigned to Priority 1 retains a certain level, the transactions will be routed back to the gateway assigned to Priority 1.
In addition to routing mechanisms explained above, Optimizer also allow you to add gateways in order of priority while creating custom rules. Our AI-ML algorithm monitors the traffic constantly and route the transactions to best performing gateway considering your priority order. Algorithm creates a temporary downtimes for 20 minute when SR reduces a particular threshold for high priority gateways and start routing transactions to next gateway as per the priority and its performance. This ensures that payment processing remains smooth and uninterrupted for your customers, even if some payment gateways are experiencing issues. For example, if the success rate (SR) of a gateway assigned to Priority 1 drops below a certain level, transactions will be automatically routed to the gateway configured at Priority 2.
When the SR of the gateway assigned to higher priority retains a certain level, the transactions will be routed back to those gateways.
Do vet the content from some else too to see others can also understand who don;t know the feature
transactions will automatically be routed to the gateway assigned to Priority 2
transactions will be automatically routed to the gateway configured at Priority 2
all
remove this
particular
remove this
Optimizer allows you to assign priority levels to all your transactions.
Optimizer allow you to add gateways in order of priority while creating custom rules.
Watch Out!Manual Capture settings only apply to payments processed via Razorpay and do not apply to any external payment gateway.
This is not required. We have complete separate section below for manual capture
settle it
settle the amount
Manual Capture settings only apply to payments processed via Razorpay.
Remove this. Same as first point
After the capture, the amount is settled to your account as per the settlement schedule.
remove this as optimizer do not deal with money movement
Watch Out! The time frame set for Manual Capture will not apply to payments processed via external gateways. Even if you have set a manual capture setting for any number of days, the payment will be auto-refunded as per the time frame set for Auto Capture. Manual Capture settings only apply to payments processed via Razorpay.
Manual Capture settings only apply to payments processed via Razorpay.
Optimizer will auto capture the payment if the payment is authorised within a certain time period.
Any payment authorised after that time period (auto capture time period) will be auto refunded.
Any manual capture time period set on the Razorpay dashboard will not be used for payments processed via payment providers other than Razorpay. Such payments will be auto captured by default.
This is important to reflect the correct information as downstream payment providers will mark the payment as successfull and will settle to your account as per the settlement schedule even if Optimizer will wait for you to capture the payment manually.
Auto-capture + Manual Capture Timeouts
Make this heading as separate heading of page, not under Auto capture with custom timeout
And rename it to
Manual Capture Timeouts
Configure Payment Capture Settings Using Orders API Capture values passed in the Orders API take precedence over the Payment Capture settings configured on the Razorpay Dashboard. You can use this to change the capture settings for individual payments.
Remove this section too
Let us say you want to: Auto-capture payments that are authorized within 2 days from creation. Manually capture payments that are authorized within 3 days from creation. Capture SettingsSelect Automatic Capture Automatic capture timeout = 2 days.Manual capture timeout = 3 days.Payments auto-refunded ifPayments not captured by you within 2 days. Payments are authorized after 3 days. Watch this video to see how to set up the Automatic and Manual Capture with Timeout option. To configure capture settings: Log in to your Dashboard. Navigate to the Account & Settings → Capture and refund settings (under Payments and refunds section). Click Change next to Automatic Capture. Under Automatic Capture, click the drop-down and select the time period in the Capture all payments authorised within field. For example, 2 days. Click Next. Select Capture manually via dashboard or API. Click the drop-down and select the time period in the Capture payments manually authorised within field. For example, 3 days. Click Next. Click Normal Speed and Save.
Remove this entirely
and manual
remove this
manually capture payments that are authorized after that time period.
Remove this line and change this to
auto refund the payments that are authorised after that time period
Payment Capture settings are applicable only for payments created using the Orders API. For Direct Settlement merchants, payments will be auto-captured even if they are created without using the Orders API.
Remove both the points
Manual capture timeoutAllows you to define custom manual capture timeout.The minimum value is 12 minutes. The maximum value (default) is 5 days.
Remove this section
You must ensure that all payments in the authorized state are moved to captured state within 5 days of creation. This is mandatory because payments that are not captured within this time period will be refunded automatically to customers.
System ensures that all payments in the authorized state are moved to captured state within 5 days of creation. This is mandatory because payments that are not captured within this time period will be refunded automatically to customers.
Late authorization
Remove this heading as included this in above line
However, the payment can remain in the authorized state in the following scenarios:
However, the payment can remain in the authorized state in case of late authorization
Specific business use case Some businesses such as those in the Ecommerce industry, may retain the payment in the authorized state and later move them to the captured state.
Remove this point completely
Razorpay
Optimizer
from the bank
remove this
Due to external factors such as network issues or technical errors
Due to external factors such as network issues, or issues at payment provider
Razorpay
Optimizer
Razorpay
Optimizer
, either manually or automatically
remove this
by Razorpay
remove this
Razorpay
Optimizer
Razorpay
Optimizer
Configure auto payment capture settings from the Razorpay Dashboard and using APIs.
Configure auto refund settings from the Razorpay Dashboard and using APIs
Let us assume you want to set up a custom rule wherein you want to route all payments coming from a particular referrer code (custom identifier) to a particular payment gateway (for example, Paytm).
Route all payments coming from a particular referrer code to a particular payment gateway like Paytm using custom identifier.
custom identifiers
link this with https://betasite.razorpay.com/docs/razorpay/IN/Optimizer-Home-Page-Update/payments/optimizer/create-custom-rule#custom-identifiers
• Channels (Website, Android, iOS) • Payment Method (Card, Netbanking, UPI Intent and UPI Collect) • BIN Number (Card IIN Number) • Card Type (Debit, Credit, Prepaid, Corporate) • Card Brand (American Express, Diners Club, Discover and so on) • Card Issuer (SBIN, HDFC, ICIC, UTIB, KKBK) • Banks (SBIN, HDFC, ICIC, UTIB) • Amount (In Paise)
Better spacing between bullet points
And amount is in Rs
For Card issuer and Banks write , so on in list of banks and issuers
Let us assume you want to set up a custom rule wherein: Priority LevelsTransaction Split - Payment Gateway/ProviderPriority 1• 70% of transactions to be routed via Paytm • 30% of transactions to be routed via RazorpayPriority 2• 100% of transactions to be routed via PineLabs This means that if the transaction attempted through Paytm and Razorpay fails in Priority 1, then as per Priority 2, the transaction will be re-attempted through PineLabs. Watch this video to see how to perform method-based routing.
Same here without priority
Example 1 Let us assume you want to set up a custom rule wherein: Priority LevelsTransaction Split - Payment Gateway/ProviderPriority 1• 80% of transactions to be routed via Paytm • 20% of transactions to be routed via PayUPriority 2• 100% of transactions to be routed via Razorpay This means that if the transaction attempted through Paytm and PayU fails in Priority 1, then as per Priority 2, the transaction will be re-attempted through Razorpay. Watch this video to see how to perform channel-based routing.
Told you not to have priorities.
Put some sample example without priority in both table and gif
payment
payments
transactions
remove this
In addition, fallback priority levels can be configured. This means that if a transaction assigned as Priority 1 fails, a secondary fallback Priority 2 can be established to ensure the transaction is redirected appropriately. This provides a level of redundancy and flexibility in the routing process.
Remove this
Add this new heading after payment parameters, above smart routing
Custom Identifiers
Apart from regular payment parameters, you might need to route payments to a particular gateway basis some business logic defined at your end like customer or product information. You can use custom identifiers for such requirements to pass the value to us while creating order and use it to create custom rule
Add one example
Custom Identifiers Know more about Custom Identifiers.
Remove this
Custom Identifiers
Remove this
You can create a set of customised rules for your transactions on the basis of various parameters.
Custom rules provides you the capability and flexibility to define your business rules using various payment parameters.
Shift the example before the Supported Payment Parameters
of
remove this
All your paymnets will have a standard rule set by default. You can edit this rule as per your business requirement. With Standard Routing you can: Set basic priority for all your payments. Prioritise the gateways for all your transactions. You can set the basic priorities and manage the payment gateways by using the Default Rule. This default rule acts as a backup plan, ensuring that all transactions have a path for processing even if they do not meet the criteria specified in any of the rules.
You might not have special routing needs for all your payments. A very simple routing rule could be to set the gateway priority which will work for all the payments. This can be accomplished using the default rule.
With Standard Routing you can: * Prioritise the gateways for all your transactions. * Distribute load among the gateways like 50% to payment A and rest 50% to payment gateway B.
prerequisites
pre-requisites
We support a range of bank gateways and payment providers
We support a range of bank gateways and aggregators
Banks like Axis, ICICI, HDFC, and so on, which provide their own payment gateway accounts to accept payments. While aggregators work with banks and provide you with the ability to accept a wide range of payments.
Banks like Axis, ICICI, HDFC, and so on provide their own payment gateway accounts. While aggregators work with banks and provide a wide range of payments methods.
Bank Gateways and Aggregators are the two types of payment service providers.
Bank Gateways and Aggregators are the two types of payment providers.
,
. We Add hyperlink to bank gateways and payment providers
We support a range of payment methods and payment providers.
Remove this
You can add Payment Providers on the Razorpay Dashboard by submitting details through a self-serve flow.
There are two kinds of payment service providers - Bank Gateways and Aggregators. Banks like Axis, ICICI, HDFC, etc which provide their own PG accounts to accept payments. While Aggregators work with Banks and provide you with the ability to accept wide range of payments. We support a range of bank gateways and payment providers
You can add Payment Providers by adding few details on the Razorpay Dashboard. Every provider has a different set of prerequisites and details. Before adding provider, you will have to ensure that the PG/Aggregator is ready and has completed all the pre-requisites.
Watch this video to see how to add Cashfree as a provider
Add steps below the video like this https://razorpay.com/docs/payments/payment-links/create/
This is a secure process, where access is restricted and the details are not shared internally for any purpose other than supporting your integration. Know more about Razorpay Security.
This is not required
Each gateway has a different set of prerequisites that you should adhere to. The video given below shows how to add Cashfree as a provider:
Add steps below the video like this https://razorpay.com/docs/payments/payment-links/create/
which is available on your dashboard
which is only visible on your dashboard
,
remove this
Razorpay Optimizer allows you to set up customized rules for routing transactions through multiple payment gateways. These rules can be configured based on the specific requirements of your business. Additionally, Razorpay Optimizer allows you to dynamically route transactions using various available parameters, ensuring that transactions are processed through the most appropriate payment gateway based on various factors such as payment method, amount, issuer, and more.
Create your rules on Razorpay dashboard to dynamically route transactions using different parameters like payment method, amount, issuer, and more. You can also add the priorities in every rule to ensure transaction is routed to the best performing gateway
This process is secure, as access is limited and your information is not shared internally for anything other than assisting with your integration.
This process is secure, and the details added by you are fully encrypted which is available on on your dashboard.
for adding
to add
payment
remove this
Partial payments Allow your customers to make partial payments. You can also decide the first installment amount to be paid by customers in case of partial payments.
Remove this!! Some copy paste
Seamlessly optimize success rates with priorities and a smart router.
Seamlessly optimize success rates using gateway priority and smart router.
Advantages
Ease Integration Optimizer is available on the fly with your existing Razorpay integration making it simple for businesses to start optimizing their payment transactions.
Real time Optimization Razorpay Optimizer uses real-time data to optimize payment routing, ensuring that transactions are routed to the best available acquirer or gateway.
Improved Success Rate By using real-time data, Razorpay Optimizer helps to reduce the number of failed transactions and improve Success rate.
Better Customer Experience Optimizer seamlessly routes the transaction to the bext performing gateway entirely through the backend without any customer intervention.
Merging multiple points.
Optimize success rates and cost. Distribute traffic across payment providers. Add payment providers within rule priorities as fallback.
Watch this video to know what is Razorpay Optimizer.
Watch this video to see what Optimizer offers.
Video Tutorial
Separate section not required
You can create different rules based on payment methods, channels, card IIN number, card type, card brand, card issuer, banks and transaction amount.
You can create different rules based on various parameters like payment methods, channels, card IIN number, card type, card brand, card issuer, banks, transaction amount and so on.
You can also set up rules to route the transactions to them using various parameters like method, amount, issuer and so on.
You can set up your own rules to route the transactions to different payment gateways. With every rule, you can also add your gateway priority which will be used if the higher priority gateway is facing any downtime/service degradation
This helps ensure a higher success rate when processing transactions.
This will help you to optimize payment processing cost and also ensure a higher success rate.
Select Billdesk in the list of gateways available and click Next.
Change this image too
Configure
Change this to Enable
n the Cashfree Dashboard, select the old version for webhook responses.
On the Cashfree Dashboard, select the v0 version for payment success, pending and fail state events.
Know how to save customer card details as tokens on Optimizer using Razorpay's TokenHQ solution.
Know how to save customer card details as tokens with multiple payment partners using Optimizer.
Watch Out! If a merchant is a Token Requestor(TR) and tries to process a payment through PayU, the payment will not be processed. To enable this, please contact us at payments_optimizer@razorpay.com.
If a merchant requests a token from payment partner other than Razorpay and tries to process the payment via other payment partner, please get in touch with us at … We’ll help you with the extra token attributes required by the payment partner to process the payment.
e Card Payment Flow🔗
Both the Images for step 7
Coming Soon Paytm Coming Soon
Make them Live
d Payment Flow🔗
In both the flows, step 7 should be only Payment response
For token details another flag is required which we are not discussing in this doc
If a merchant is a Token Requestor(TR) and tries to process a payment through PayU, the payment will not be processed. To enable this, please contact us at
If a merchant is a Token Requestor(TR) and token is generated from payment partners other than Razorpay and tries to process a payment through payment partners other than Razorpay, please contact us at ... We might need few extra token attributed required to process payment through other payment partners.
Razorpay offers an end-to-end RBI-compliant solution that allows you to save customer credentials as tokens with card networks and card-issuing banks
Razorpay Optimizer offers an end-to-end RBI-compliant solution that allows you to save customer credentials as tokens with card networks and issuing banks and process payments through any PA/PG.
the payment must be completed from the merchant or the external gateway.
the payment can be processed via Razorpay or external gateways.
Given below are a few examples of Optimizer Tokenisation flow when Razorpay is the Token Requestor.
Given below is the Optimizer Tokenisation flow when Razorpay is the Token Requestor.
You can use Optimizer and process payments on Razorpay and external gateways
You can use Optimizer with Razorpay as Token Requestor and process payments on Razorpay and external gateways
We initiate the tokenisation request at checkout.
This is not required. Already added in step 3
Feature Enablement This is an on-demand feature. Get in touch with us to get this feature enabled on your account.
Not required
If you do not wish to enable Tokenisation for Optimizer, you won't be able to use saved card flow on standard checkout.
Not required
If you have enabled Tokenisation for Optimizer, you must redirect cards traffic to the supported payment gateways only. Know more about supported payment gateways.
If you are using save card feature, you must redirect cards traffic to the supported gateways only. Know more about supported payment gateways
To enable tokenisation for external gateways on Razorpay Optimizer, please contact your external gateways support.
This is not required
With this solution, you can: Process payments through any PA/PG while tokenising cards through Razorpay. Use Razorpay Optimizer to route payments through the PA/PG of your choice.
Remove this. Added this context above
details
and you can process these payments through any PA/PG as per your business requirements.
Enable ENACH for your account.
if you want to use eMandate payments.
issues at the customers bank, UPI apps or wallets.
at customer's bank, UPI Apps, external gateways, etc
to t
occur due to issues at business side like non
analyse
compare
as All Banks
like All Banks
analyse
compare
as per
like
analyse
compare
transactions as
further filter the view like
various
various is not required
Analyse the contribution of each payment gateway or provider to overall payments. View the payment volume distribution with the help of a pie diagram
What is the difference between these two statements?
NetBanking
Make all the changes as per suggestion in UPI for all the sections
ayment providers breakdown of the total success rate with the hel
incorrect
View the graphical presentation of all the payment providers for Cards transactions by selecting the individual payment provider label or overall label as per your requirement.
Change this as per above suggestion
as mentioned above
This is not required
of the total success rate
Again, not SR breakdown, its payment volume distribution
failure reasons
top failure reasons
View the payment method level breakdown of the payment volume distribution with the help of a pie diagram.
breakdown and distribution cannot come together
View the payment volume distribution at method level with the pie chart.
You can also view the above information in graphical representation.
The line graph show the SR distribution on Hourly, daily, weekly on Monthly basis as per your date range selection.
for graphical representation
Additionally, in SR line graph you can select the time frame for hourly, daily, weekly, and monthly basis
most top
most is not required here
r overall label as
Lets change this screenshot to show multiple gateways
high-level view of all UPI transactions and recent performance along with the payment providers details.
for the selected date range
View the success rate
First and second point are repeat information
tile
You can select the date and time range to do the Success Rate analysis by using a predefined list or set custom time range.
success rate breakup
This is not SR breakup. This is payment volume distribution wrt methods (when all method tile is selected) and gateways (when method tile is selected)
payment method level
This does not happen in Optimizer SR dashboard
significant
View the top reasons or View the most frequent reasons
upported providers
Below is list of Wallets,not provider
We have to add both wallets and which provider support which wallet
If you want your unique identifier (Order ID) to be visible on PayU's dashboard, write to your PayU Relationship Manager asking to make the specific column (the one having your Order Id) visible on the dashboard. Know more about how to send your order id to Payu.
To pass your unique Order ID or Receipt for every order, write to your relationship manager to show the 'xyz' parameter in PayU Dashboard and customize report. Know more about how to send your Order ID to PayU
same value to PayU
in 'xyz' parameter
Add which parameter we are using to send the receipt value
Razorpay passes this value to PayU in 'xyz' parameter
(Parameter name should be available in jira ticket
Next point Write to your PayU Relationship Manager to show this parameter (xyz) in dashboard and reports as per your use case (usage)
In the receipt parameter, enter the Order Id you want to be visible on the PayU's dashboard.
Send your unique Order ID or Receipt in the receipt parameter of Orders API.
A unique order id is generated whenever a payment is processed via Optimizer. This order id will not be visible on the PayU's dashboard as it is specific only to the merchant. You can pass your Order Id to PayU using Razorpay's Orders API.
You might be generating a unique Order ID or Receipt for every order which can be passed to PayU via Orders API (with a link).
Send Merchant Order ID to External Gateway🔗
Send Receipt/Order ID to External Gateway
according to
as per
Credits
Where we'll add the gif/videos on this page?
TDR charges
This URL is on S3. If we need to expose this, we should change the URL
These credits are available only for specific business categories to help them meet regulatory requirements.
Credits are available for all. But generally useful for such business categories
add
view/add
Refund speed for payments that were not captured (automatically or manually). Possible values:
Font
Time in minutes till when you can manually capture payments in the authorized state.
Font issue
Time in minutes till when payments in the authorized state should be auto-captured.Minimum value 12 minutes
Font is different from entire doc
orders
Add this for Go. You'll have to do the indentation. And for all the languages have provided the import statements. Add a line gap between the import statement and next code.
import ( razorpay "github.com/razorpay/razorpay-go" )
client := razorpay.NewClient("<YOUR_API_KEY>", "<YOUR_API_SECRET>")
data := map[string]interface{}{ "amount": 1234, "currency": "INR", "receipt": "some_receipt_id", "payment": map[string]interface{}{ "capture": "automatic", "capture_options": map[string]interface{}{ "automatic_expiry_period": 12, "manual_expiry_period": 7200, "refund_speed" "optimum'
} } }
body, err := client.Order.Create(data)
razorpay
Change this to razorpayClient
J
Remove try and opening and closing braces
RazorpayClient razorpayClient = new RazorpayClient("key_id", "key_secret");
Add this above JSONObject
D
RazorpayClient client = new RazorpayClient(key, secret);
Add this above Dictionary
Also change all add to Add
And remove bold from entire snippet
razorpay.orders.create
instance.orders.create
v
var instance = new Razorpay({ key_id: 'YOUR_KEY_ID', key_secret: 'YOUR_KEY_SECRET' })
Add this above var
order = Razorpay::Order.create
Remove this
o
require "razorpay" Razorpay.setup('key_id', 'key_secret')
Add this above order
DATA
import razorpay client = razorpay.Client(auth=("<YOUR_KEY>", "<YOUR_SECRET>"))
Add these lines above the DATA
Please the codes might change while copy paste
$order = $client->order->create
use Razorpay\Api\Api;
$api = new Api($api_key, $api_secret);
$order = $api->order->create
n this case, Razorpay polls the APIs intermittently to check the status. Once the bank confirms it to be successful, the payment attains authorized state.
In this case, Razorpay polls the Bank APIs intermittently for 5 days to check the status. If we receive the payment status from the bank as Successful, the payment moves to the authorized state.
Same as other link
override
The options sent in the below API take precedence over the account level auto-capture settings configured using the Dashboard.
Can we change this statement to avoid using override. And use something like this. This is from in API doc
Once a payment is created, you can auto-capture payments that are authorized within a certain time period and manually capture payments within a time period beyond that.
Once the payment is created, you can auto-capture payments that are authorized within a certain time and beyond that manually capture payments within a set time.
Right now, beyond that positioning is giving a feel of something after manually capture. What do you think?
Payments are auto-refunded if ● Payments are not captured by you within 3 days.● Payments are authorized after 3 days.
Same logic apply here. Use above sample
capture authorized
Add all here.
capture all authorized
Payments are auto-refunded if ● Payments are not captured by you within 3 days.● Payments are authorized after 3 days.
Here "are" is repeating both sides. It could be (also aligning with above one),
Auto-refunded payments - Payments authorized after 3 days / Payments not captured by you within 3 days
Payments are auto-refunded if Payments authorized after 2 days are auto-refunded.
Auto refunded is repeating here in both sections
It could be something like this,
Auto-refunded payments - Payments authorized after 2 days
In this case, Razorpay polls the APIs intermittently to check the status. If the bank confirms payment success, the payment is moved to authorized state.
In this case, Razorpay polls the Bank APIs intermittently for 5 days to check the status. If we receive the payment status from the bank as Successful, the payment moves to the authorized state.
Payments in the authorized state after the timeout are auto-refunded.
Payments in the authorized state are auto-refunded after the timeout.
Allows you to define custom auto-capture and manual capture timeouts. ● Minimum value is 12 minutes. ● Maximum value (default) is 5 days. Manual capture timeouts Allows you to define custom auto-capture and manual capture timeouts.● Minimum value is 12 minutes.● Maximum value (default) is 5 days
Description in these two sections is exactly same.
and if manual capture timeouts is representing the third option(Manually capture with set timeouts) then there is no need to mention auto capture in this section.
Have a look and make changes accordingly.
Once the bank confirms it to be successful, the payment attains authorized state. Learn more about late authorization.
This does not look correct. (Bank confirm it to be successful) And attains is difficult word
It could be, payment is moved to authorized state. Some simple statement
your
your is repeating twice. We can make it "as per the settlement schedule"
Note:
This Note should come after Request parameters are explained