- Feb 2022
-
betasite.razorpay.com betasite.razorpay.com
-
alternate
alternative
-
alternate
alternative
-
Note🔗
Use Heading 2 UPI Collect Requests
-
or Subscriptions🔗
Use Heading 2
-
Watch Out! For Swift version 5.1+, ensure that you declare var razorpay: RazorpayCheckout!. For versions lower than 5.1, you may use var razorpay: Razorpay!. Alternatively, you can use the following alias and retain the variable as Razorpay. typealias Razorpay = RazorpayCheckout
Same comments as for Standard
-
If you are building an Objective-C project, follow the steps given for Swift and the additional steps given below: Go to Project Settings and select Build Settings - All and Combined. Set the Always Embed Swift Standard Libraries option to TRUE. Ensure that you have the framework added in both Embedded Binaries and Linked Frameworks and Libraries under Target settings - General. For Xcode 11, ensure that you have the framework added in Frameworks, Libraries, and Embed Content under Target settings - General. Change Embed status from - 'Do not Embed' to 'Embed & Sign'.
Same comments as for Standard
-
Additional Steps for Objective-C🔗
Use heading 2
-
your project🔗
Your Project
-
-
betasite.razorpay.com betasite.razorpay.com
-
Watch Out!+:
remove plus, bold Watch Out
-
Handy Tips
bold Handy Tips
-
For Swift version 5.1+, ensure that you declare var razorpay: RazorpayCheckout!. For versions lower than 5.1, you may use var razorpay: Razorpay!.
bullet these
-
Initialize the Razorpay iOS Standard SDK🔗
remove the
-
Handy Tips We now support another optional parameter to the open method - displayController. When this parameter is specified, the Razorpay controller is pushed on to this controller's navigation controller if present or presented on this controller if absent. For example, the Swift call is: razorpay.open(options, displayController: self)
Optional Parmeter - displayController When the optional parameter- displayController, is specified, the Razorpay controller is pushed on to this controller's navigation controller if present or presented on this controller if absent. For example, the Swift call is: razorpay.open(options, displayController: self) [Can we simplify the explanation?)
-
Possible values for failure code are:
Failure Codes
-
For Xcode 11, ensure that you have the framework added in Frameworks, Libraries, and Embed Content under Target settings - General. Change Embed status from - 'Do not Embed' to 'Embed & Sign'.
Xcode 11 [Use Heading 3] Ensure that you have the framework added in Frameworks, Libraries, and Embed Content under Target settings - General. Change Embed status from - 'Do not Embed' to 'Embed & Sign'. [mention what is the gif below indicating]
-
Objective-C:🔗
Heading 2, remove colon
-
Manual🔗
Heading 2
-
Cocoapod🔗
Use Heading 2
-
You can import the SDK: - Using CocoaPod - Manually
You can import the Razorpay iOS Standard SDK library using any of these ways: Cocoapod, Manual and Objective-C.
-
Cocoapod🔗
Heading 2
-
1.1 Import the
remove the
-
-
betasite.razorpay.com betasite.razorpay.com
-
license
hyperlink the word "license" http://www.gnu.org/licenses/old-licenses/gpl-2.0.html
-
You can also refer to the license text in the license file on GitHub.
Check the license text in the license file on GitHub.
-
the same as WordPress.
remove
-
with
With
-
-
betasite.razorpay.com betasite.razorpay.com
-
Follow these steps
remove
-
Follow these steps
remove
-
-
betasite.razorpay.com betasite.razorpay.com
-
Generate the API keys from the Razorpay Dashboard by navigating to Settings → API Keys. You can use the Test mode keys for testing and later switch to Live mode keys when going live with the integration.
hyperlink API keys
-
Download the Gravity Forms plugin.
hyperlink Gravity Forms
-
with
With
-
-
betasite.razorpay.com betasite.razorpay.com
-
Create a Razorpay Account.
Make this bullet 1
-
Integrating Razorpay with CS-Cart
Integrate With CS-Cart Website
-
-
betasite.razorpay.com betasite.razorpay.com
-
betasite.razorpay.com betasite.razorpay.com
-
System.
Remove the full stop
-
-
betasite.razorpay.com betasite.razorpay.com
-
hese steps:
Number steps
-
Continuing
remove
-
Then
remove
-
o this:
number steps
-
en below:
number the steps
-
at present
remove
-
2 Link the SDK🔗
Link SDK
-
sing Yarn🔗
Using
-
using NPM🔗
Capitalise Using
-
-
betasite.razorpay.com betasite.razorpay.com
-
This version of the Razorpay-React Native SDK supports Xcode 10. We have fixed the known issues of React Native on Xcode 10 in the current version of our SDK. This can be implemented until the next release of React Native.
add a colon after the version number: This version of the Razorpay-React Native SDK supports Xcode 10. The known issues of React Native on Xcode 10 are fixed in the current version of our SDK.
-
React version 16.5.0
Why are we adding this?
-
-
betasite.razorpay.com betasite.razorpay.com
-
. Know more.
Comment same as standard
-
Follow these steps to unhide the navigation bar.
Follow the steps to unhide the navigation bar. Hyperlink unhide the navigation bar.
-
-
betasite.razorpay.com betasite.razorpay.com
-
Know more.
Check the limitations. link the word limitations
-
manual linking:
Number the steps
-
For Android:
Heading 4, remove colon
-
For iOS (without CocoaPods):
Heading 4, remove colon
-
For iOS (via CocoaPods):
Use Heading 4 and remove the colon
-
Install the SD
these should be numbered steps
-
-
betasite.razorpay.com betasite.razorpay.com
-
Refer to the post-integration steps.
alignment issue
-
-
betasite.razorpay.com betasite.razorpay.com
-
Call the Ra
Numbering issue
-
Refer to the post-integration steps.
align it properly
-
You will need to
remove
-
-
betasite.razorpay.com betasite.razorpay.com
-
WhatsApp
Also fix the left nav.. Call it WhatsApp
-
Installing the Razorpay WhatsApp Bot for Payment Links enables you to accept payments from your customers by creating and sharing payment links to them from WhatsApp directly.
You can install the Razorpay WhatsApp Bot for Payment Links and accept payments from your customers by creating and sharing Payment Links to them directly from WhatsApp. Less
-
-
betasite.razorpay.com betasite.razorpay.com
-
Add Company Logo. Disable Checkout in Full Screen.
remove full stops
-
-
betasite.razorpay.com betasite.razorpay.com
-
.
use colon
-
are
remove
-
Error codes
Error Codes
-
Other Checkout form fields🔗
Other Checkout Form Fields
-
-
betasite.razorpay.com betasite.razorpay.com
-
will throw
throws
-
will auto-read it.
auto-reads it
-
then
remove
-
Razorpay Android Standard SDK lets you easily integrate the Razorpay Payment Gateway with your Android application.
You can use Razorpay Android Standard SDK to integrate the Razorpay Payment Gateway with your Android application.
-
with
With
-
-
betasite.razorpay.com betasite.razorpay.com
-
-
Use colon
-
Customize order of Apps🔗
Customise Order of Apps
-
For additional support on Payment Methods, such as fetching bank or wallet logos, fetching card network and information on how to validate card information, read Additional support for Payment Methods.
Additional Support for Payment Methods: fetching bank or wallet logos, fetching card network and information on how to validate card information.
-
In this case
In Collect Flow,
-
Implement PaymentResultWithDataListener Method🔗
- Implement PaymentResultWithDataListener Method🔗
-
Create Payment🔗
- Create Payment
-
Detect Presence of CRED App🔗
- Detect Presence of CRED App
-
In the sample code below, BHIM (in.org.npci.upiapp) is passed in the preferred apps list and Google Pay(com.google.android.apps.nbu.paisa.user) in other apps list. As a result, BHIM is shown in the PREFERRED APPS SECTION. Google Pay is shown at the top in the OTHER APPS SECTION followed by other apps present in the device:
Sample Code [Heading 4] In the sample code below, BHIM (in.org.npci.upiapp) is passed in the preferred apps list and Google Pay(com.google.android.apps.nbu.paisa.user) in other apps list. As a result, BHIM is shown in the PREFERRED APPS SECTION. Google Pay is shown at the top in the OTHER APPS SECTION followed by other apps present in the device:
-
OTHER APPS Section Similar to PREFERRED APPS section, the list of applications as specified using the key other_apps_order within options is displayed under this section. Any unspecified app (which supports UPI intent) appears subsequent to the list passed in the options.
The list of applications specified using the key other_apps_order within options is displayed under this section. Any unspecified app (which supports UPI intent) appears subsequent to the list passed in the options.
-
PREFERRED APPS Section This section will display the list of applications as specified using the key preferred_apps_order within options. If no application exists for this key, this section will not be shown.
This section displays the list of applications specified using the key preferred_apps_order within options. If no application exists for this key, this section is not displayed.
-
Preferred Apps Other Apps
remove
-
When using intent flow, you can customize the order in which UPI apps appear on the Checkout. There can be two sections within the app chooser:
In the Intent Flow, you can customise the order in which UPI apps appear at the Checkout. There are two sections within the app: Preferred Apps and Other Apps.
-
Customize the order of Apps🔗
Customise Order of Apps
-
A complete list of UPI supported apps and their package names is available here.
Check the complete list of UPI supported apps and their package names.
-
will be
is
-
In this case
In Collect Flow,
-
The sample code below will send collect request to gaurav.kumar@exampleupi handle.
Sample Code [Heading 4] The sample code below sends a collect request to gaurav.kumar@exampleupi handle.
-
will be
is
-
In the case of
For
-
The sample code shown below allows the checkout to perform a wallet transaction for a payment of ₹299.35:
Sample Code. [Heading 4] The sample code shown below allows the checkout to perform a wallet transaction for a payment of ₹299.35:
-
Learn
Know more
-
The sample code shown below allows the checkout to perform a netbanking transaction for a payment of ₹299.35:
Sample Code [Heading 4] The sample code shown below allows the checkout to perform a netbanking transaction for a payment of ₹299.35:
-
In the case of
For
-
The sample code shown below allows the checkout to accept a card payment of ₹3999.35:
Sample Code. [Heading 4] The sample code shown below allows the checkout to accept a card payment of ₹3999.35:
-
In the case o
For
-
The sample code shown below allows the checkout to accept a card payment of ₹299.35:
Sample Code [Use Heading 4] The sample code shown below allows the checkout to accept a card payment of ₹299.35:
-
In the case of
For
-
Android Custom Integration - Payment Methods
Payment Methods
-
-
betasite.razorpay.com betasite.razorpay.com
-
-
Use Colon
-
-
Use colon
-
Learn how to integrate the different payment methods using Razorpay Android Custom SDK in detail.
Check the various payment methods available with Razorpay Android Custom SDK. [Hyperlink payment methods]
-
You can accept payments through UPI, credit and debit cards, netbanking and wallets, depending on the methods enabled for your account. When you use Razorpay Android Standard SDK, you do not have to handle the availability of different payment methods. However, when creating a Custom checkout form, you must ensure that only the methods activated for your account are displayed to the customer. To get a list of available payment methods, call getPaymentMethods. This fetches the list of payment methods asynchronously and returns the result in JSON format in the onPaymentMethodsReceived callback. For the structure of the JSON result, you can refer to this doc.
You can accept payments through UPI, credit and debit cards, netbanking and wallets, as per the methods enabled on your account.
- When you use Razorpay Android Standard SDK, you do not have to handle the availability of different payment methods.
- When creating a Custom checkout form, you must ensure that only the methods activated for your account are displayed to the customer. To get a list of available payment methods, call getPaymentMethods. This fetches the list of payment methods asynchronously and returns the result in JSON format in the onPaymentMethodsReceived callback. For the structure of the JSON result, you can refer to this doc. [link to doc does not look right]
-
Set Up the Webview🔗
Set Up Webview
-
PaymentResultListener provides only payment_id as the payment result. PaymentResultWithDataListener provides additional payment data, such as email and contact of the customer, along with the order_id, payment_id, signature and more. JavaCopy
- PaymentResultListener provides only payment_id as the payment result.
- PaymentResultWithDataListener provides additional payment data such as email and contact of the customer, along with the order_id, payment_id, signature and more.
-
Using PaymentResultWithDataListener🔗
Use PaymentResultWithDataListener🔗 [Use Heading 2]
-
Store the Fields in Server🔗
Store Fields in Server
-
Once you have successfully completed the integration, you can setup webhooks, make test payments, replace test key with live key and integrate with other APIs.
After you have successfully completed the integration, you can set up webhooks, make test payments, replace test key with live key and integrate with other APIs. [Hyperlink the correct articles here]
-
Integrate the Payments Rainy Day Kit🔗
Integrate Payments Rainy Day Kit
-
The following is a sample API request and response for creating an order:
Sample Code [Heading 4] The following is a sample API request and response for creating an order:
-
The sample AndroidManifest.xml file with auto-OTP reading feature enabled is shown below:
Sample Code [User Heading 4] For additional support on Payment Methods, such as fetching bank or wallet logos, fetching card network and information on how to validate card information,
-
Initialize🔗
Use Heading 2
-
Instantiate🔗
Use Heading 2
-
will add
adds
-
-
betasite.razorpay.com betasite.razorpay.com
-
m SDK
Also have a few suggestions for left navigation. Please incorporate all the review comments after which we can have a call and set the Left Navigation.
-
Learn more about TLS versions.
Check the TLS versions .
-
Learn
Know
-
for
remove
-
to:
remove, add a full stop.
-
,
and
-
with
With
-
-
betasite.razorpay.com betasite.razorpay.com
-
To create a payment with an existing saved card, you have to pass the token instead of the card number, expiry and card holder's name fields as shown below:
Create a Payment With Existing Saved Card [Use Heading 2] To create a payment with an existing saved card, you have to pass the token instead of the card number, expiry and card holder's name fields as shown below:
-
Later, while creating a payment with new card, you would need to pass the customer_id and save as extra fields, along with the other fields as shown below:
Create a Payment With New Card [use Heading 2] While creating a payment with new card, you would need to pass the customer_id and save as extra fields, along with the other fields as shown below:
-
as well:
remove
-
The sample code given below shows how to customize the RazorpayWebViewClient:
Sample Code [Heading 4] The sample code given below shows how to customize the RazorpayWebViewClient:
-
The sample code shown below describes a validation error on the contact field:
Sample Code [Use Heading 4] The sample code shown below describes a validation error on the contact field:
-
A failure response is triggered in the case of any exceptions.
Add this along with the previous paragraph
-
At least 6 digits of the card number are required to identify the network. Possible values returned by this method are: - visa - mastercard - maestro16 - amex - rupay - maestro - diners - unknown If it is not able to identify the network it returns unknown.
- At least 6 digits of the card number are required to identify the network.
- Possible values returned by this method are visa - mastercard - maestro16 - amex - rupay - maestro - diners - unknown.
- If it is not able to identify the network it returns unknown.
-
: -
remove
-
Here are some of the methods provided by the SDK that can be used for card payment method integration.
You can use these methods for card payment method integration.
-
The Razorpay Android Custom SDK lets you integrate supported payment methods on the Checkout form of your Android app as per your business requirements. Here are some additional methods provided by the SDK for the integration and usage of payment methods:
Use the Razorpay Android Custom SDK to integrate supported payment methods on the Checkout form of your Android app as per your business requirements. Here are some additional methods provided by the SDK for the integration and usage of payment methods:
-
-
betasite.razorpay.com betasite.razorpay.com
-
Given below is a sample code for overriding minSDK version.
Sample Code to Override minSDK Version [Heading 4]
-
minSdkVersion is the minimum version of the Android operating system required to run your application. The Android app must have a minimum SDK version 19 or higher. If you want to support devices below API level 19, you must override minSDK version.
- minSdkVersion is the minimum version of the Android operating system required to run your application. The Android app must have a minimum SDK version 19 or higher.
- If you want to support devices below API level 19, you must override minSDK version.
-
Android Custom Integration - Override Minimum SDK Version
Override Minimum SDK Version
-
-
betasite.razorpay.com betasite.razorpay.com
-
Android Custom Integration - Proguard Rules
Proguard Rules
-
-
betasite.razorpay.com betasite.razorpay.com
-
Accept Live Payments
Use Heading 1
-
Poll APIs🔗
Poll APIs [Heading 2]
-
red URL.
Know how to set up webhooks.
-
Subscribe to Webhook events
Subscribe to Webhook Events [Use Heading 2]
-
From the Dashboard🔗
From Dashboad [Use Heading 2]
-
subscribe to the Webhook event or poll our APIs.
by subscribing to Webhooks or polling our APIs.
-
Verify the Payment Status🔗
Verify Payment Status [Heading 1]
-
Test Cards🔗
Make this heading 2
-
Test Payments🔗
Make this Heading 1
-
Test Integration🔗
- Test Native OTP Integration [Make this a separate article after Native OTP Integration]
-
Native OTP on Android Custom Checkout
- Native OTP Integration
-
No money is deducted from the customer's account as this is a simulated transaction. In the Checkout code, ensure that you have entered the API keys generated in the test mode.
- No money is deducted from the customer's account as this is a test transaction.
- In the Checkout code, ensure that you have entered the API keys generated in the test mode.
-
on
in (for consistency)
-
Store the Fields in Server🔗
Store Fields in Server
-
PaymentResultListener provides only payment_id as the payment result. PaymentResultWithDataListener provides additional payment data, such as email and contact of the customer, along with the order_id, payment_id, signature and more.
- PaymentResultListener provides only payment_id as the payment result.
- PaymentResultWithDataListener provides additional payment data such as email and contact of the customer, along with the order_id, payment_id, signature and more.
-
Using PaymentResultWithDataListener🔗
Use Heading 2
-
,
remove comma
-
Given below is the sample code:
Replace with Sample Code [Heading 4]
-
Cancel the OTP
Cancel OTP
-
Ask for the OTP to be resent
Request for OTP to be resent
-
Submit the OTP
Submit OTP
-
If Native OTP is enabled for the BIN, you should call the razorpay.getCardOtpData(CardsFlowCallback) function. The SDK then fires the otpGenerateResponse(boolean otpGenerated) function and informs whether the OTP was successfully sent to the customer or not. Based on this information, you can display the generated OTP UI to the customer.
If Native OTP is enabled for BIN, you should call the razorpay.getCardOtpData(CardsFlowCallback) function. The SDK then fires the otpGenerateResponse(boolean otpGenerated) function and confirms if the OTP was successfully sent to the customer. Based on this information, you can display the generated OTP UI to the customer.
-
Given below is the sample code.
Replace with Sample Code [Heading 4]
-
The SDK fires the isNativeOtpEnabled function, determining whether the native OTP flow is enabled for the BIN.
The SDK fires the isNativeOtpEnabled function and determines whether the native OTP flow is enabled for the BIN.
-
Call the razorpay.getCardOtpData(CardsFlowCallback) function🔗
Call razorpay.getCardOtpData(CardsFlowCallback) Function🔗
-
1.2 Implement CardsFlowCallback interface in the getCardsFlow function
Implement CardsFlowCallback Interface in getCardsFlow Function
-
on the Razorpay Dashboard.
link to generating API keys.
-
a Razorpay account.
link as on the other page
-
in
at
-
payment gateway
Payment Gateway
-
-
betasite.razorpay.com betasite.razorpay.com
-
Once
When
-
Pass the Result to Razorpay🔗
Pass Result to Razorpay
-
Initialize the SDK by adding the API Key🔗
Initialise SDK by Adding API Key
-
Install the Razorpay Android UPI Intent SDK🔗
Install Razorpay Android UPI Intent SDK🔗
-
app.
Can we number the steps in the image? Also the screen shot is hazy.
-
your
their
-
he
they
-
he does not have
they do not need to
-
customer
customers
-
-
betasite.razorpay.com betasite.razorpay.com
-
Troubleshooting & FAQs
A lot of extra spaces around the text. Please fix all.
-
-
betasite.razorpay.com betasite.razorpay.com
-
ay customer:
Add a couple of screen shots within the steps
-
have Payment access enabled
Add a couple of screen shots within the steps
-
access enabled:
Add a couple of screen shots within the steps
-
fy Checkout.
add a screen shot
-
Login
Log into
-
pay user🔗
User
-
fy Checkout.
Add a screen shot
-
Once you login,
After you log in,
-
Once you login
After you log in,
-
Login
Log into
-
Login
Log into
-
rpay user without Payment Access🔗
Use Title capitalisation
-
pify Checkout.
add a screen shot
-
Login
Log into
-
Login
Log into
-
Existing Razorpay user
User
-
Existing Razorpay user with Payment Access. Existing Razorpay user without Payment Access. New Razorpay user.
remove the full stops
-
The integration steps differ in whether you fall under the following three categories.
remove this line
-
-
betasite.razorpay.com betasite.razorpay.com
-
Initi
create a video for this
-
Follow these steps:
To initiate refunds:
-
-
betasite.razorpay.com betasite.razorpay.com
-
Create
We should also create a video for this.
-
on
at
-
ay them on Checkout.
add a line as : To display offers at Checkout
-
-
betasite.razorpay.com betasite.razorpay.com
-
ur web page/app
Add a screen shot
-
-
betasite.razorpay.com betasite.razorpay.com
-
Integrate with Shopify Plugin (v2)
liked this heading. Should we use it consistently with all the integration documents?
-
, allowing the customer to pay on your store without being redirected. This allows the plugin to work across all browsers.
where your customers can pay directly on your website without any redirections. The plugin works across all browsers.
-
with
With
-