rewrite below.
Below is not clear
44 Matching Annotations
- Last 7 days
-
razorpay.com razorpay.com
-
-
3. How Simulation Works
This section is not needed
-
Create payment
Need to callout multiple payment attempts from user against same cart/invoice should be mapped to single order id
-
Test Mode lets you run your whole integration against simulated banks, card networks and NPCI before you take real payments.
We should also mention - Razorpay Testing Guide helps enginners team and agents write test cases that help test various edge cases in integration
-
- Dec 2022
-
betasite.razorpay.com betasite.razorpay.com
-
Create a Payment API Integration Changes
Quick Summary of changes
-
can mak
need to make
-
user
business
-
-
betasite.razorpay.com betasite.razorpay.com
-
opt_generate
otp_generate (Typo)
-
The payment request would remain same for both redirection and native OTP flows.
Lets remove this line
-
- Nov 2022
-
betasite.razorpay.com betasite.razorpay.com
-
Choose Integrationđź”—
remove this
-
Supported Authentication Channelsđź”—
remove this
-
-
betasite.razorpay.com betasite.razorpay.com
-
3
Razorpay integration is compliant with 3DS2 protocol.
-
flow
request & response
-
flow
request
-
C
Lets remove this section
-
What is 3DS2.0đź”—
3DS 2 Authentication [New]
-
Given below is a diagram that explains the 3DS2.0 flow:
Callout 1: Integration does not change for challenge or frictionless flow.
Call out 2: Frictionless flow is not applicable for payments on cards issued in India
-
Supported Authentication Channelsđź”—
Lets remove this section
-
Currently, this would not be applicable in India
Bold
-
3DS,
3DS 1
-
with the 3DS2.0 authentication protocol.
Razorpay APIs support latest 3DS2 authentication protocol.
-
with the 3DS2.0 Protocol.
Can be removed
-
with 3DS2.0 Protocol (New Users)
Can be removed
-
-
betasite.razorpay.com betasite.razorpay.com
-
Given below is an illustration of the frictionless authentication workflow:
Again flow is specific for international payments. Merchants may think this is true for domestic payments also
-
Razorpay offers 3DS 2.0 support for international card payments only.
This is no longer true.
Instead we should call out, 3DS2 is live on international payments. 3DS2 on domestic payments is currently on demand basis only. Please reach out to us for more details
-
3DS 2.0 limits potential fraud through data sharing and transaction risk analysis.
How?
-
ard-not-present (CNP)
This is not a word merchants understand. Can we use simple words like online payments?
-
hosted
Why is the word hosted sill there? We need to rework this
-
-
betasite.razorpay.com betasite.razorpay.comPayments1
-
The maximum length supported is 26 characters.
Let us remove the maximum length criteria.
-
- Oct 2022
-
betasite.razorpay.com betasite.razorpay.com
-
Razorpay supports 3D Secure 2 (3DS 2.0)
Merchant is coming to this page to integrate S2S APIs. Why does this page start with 3DS2. 3DS2 is just a feature among other feature Razorpay offers
-
The feature introduces frictionless authentication and supports a strong customer authentication (SCA) factor.
Frictionless authentication is applicable only for international payments
-
hosted
This is not a hosted solution.
-
-
betasite.razorpay.com betasite.razorpay.com
-
On the b
Feedback: - The section makes more sense in API spec as it is relevant only for them. Checkout merchants need not know this. - Again what is device channel is not defined for someone new to the 3DS2 concept. Appears out of context
-
Why is 2.0 in bracket everywhere?
-
Razorpay supports 3D Secure 2 (3DS 2.0), a hosted solution that improves the purchase experience. The feature introduces frictionless authentication and supports a strong customer authentication (SCA) factor.
Need to add more context as to why 3DS2 is important now. We need to callout that networks have mandated this change
-
frictionless authentication
Looks like incorrect heading
-
With respect to integration, only S2S integration users requires changes.
3DS 2.0 is auto-enabled for all merchants using Razorpay checkout. If you are PCI DSS compliant & have an API based integration with Razorpay, you need to make changes to your API integration.
-
Razorpay offers 3DS 2.0 support for international card payments.
Razorpay is live with 3DS 2.0 support. It is enabled by default for international card payments & enabled on request for domestic card payments.
-
- Nov 2021
-
betasite.razorpay.com betasite.razorpay.com
-
Use this API to enable your customers to add cards without any payment processing.
Lets remove this API from public spec for now
-
tokenised_card
This was later renamed to tokenised instead of tokenised_card
-
card
Expand object is not working properly
-
Use the Fetch Payment API to fetch the token.
You have added fetch payment API instead of fetch token API
-
SBIN
Check formatting
-
customer_id
Call out that this is an optional parameter
-