1. Build Integration

Steps to integrate your Custom Flutter application with Razorpay Payment Gateway.


Follow these steps to integrate your Flutter application with the Razorpay Payment Gateway:

1.1

.

1.2

.

1.3

.

1.4

.

1.5

.

1.6

.

1.7

.

1.8

.

1.9

.

1.10

.

1.11

.

Handy Tips

After you complete the integration:

  • Set up webhooks
  • Make test payments
  • Replace Test API keys with Live API keys
  • Integrate with other APIs
    Refer to the .

Watch Out!

If you use M1 MacBook, you need to make

in your podfile.

from Pub.dev.

Add the below code to dependencies in your app's pubspec.yaml:

razorpay_flutter_customui: 1.0.0

If you are using Proguard for your builds, you need to add the following lines to the Proguard files:

-keepattributes *Annotation*
-dontwarn com.razorpay.**
-keep class com.razorpay.** {*;}
-optimizations !method/inlining/
-keepclasseswithmembers class * {
public void onPayment*(...);
}

Know more about

.

Run flutter packages get in the root directory of your app.

Handy Tips

  • For Android, ensure that the minimum API level for your app is 19 or higher.
  • For iOS, ensure that the minimum deployment target for your app is iOS 10.0 or higher. Also, don't forget to enable bitcode for your project.

Use the below code to import the razorpay_flutter_customui.dart file to your project:

import 'package:razorpay_flutter_customui/razorpay_flutter_customui.dart';

For Android, use the below code to create a Razorpay instance:

_razorpay = Razorpay();

For iOS, you need to initialise and instantiate the SDK using the following method:

@override
void initState() {
_razorpay = Razorpay();
_razorpay.initializeSDK(key);
}

The plugin uses event-based communication and emits events when payments fail or succeed.

  • The event names are exposed via the constants EVENT_PAYMENT_SUCCESS and EVENT_PAYMENT_ERROR from the Razorpay class.
  • Use the on(String event, Function handler) method on the Razorpay instance to attach event listeners.
_razorpay.on(Razorpay.EVENT_PAYMENT_SUCCESS, _handlePaymentSuccess);
_razorpay.on(Razorpay.EVENT_PAYMENT_ERROR, _handlePaymentError);

The handlers would be defined in the class as:

void _handlePaymentSuccess(PaymentSuccessResponse response) {
// Do something when payment succeeds
}
void _handlePaymentError(PaymentFailureResponse response) {
// Do something when payment fails
}

Order is an important step in the payment process.

  • An order should be created for every payment.
  • You can create an order using the . It is a server-side API call. Know how to Orders API.
  • The order_id received in the response should be passed to the checkout. This ties the order with the payment and secures the request from being tampered.

Use this endpoint to create an order using the Orders API.

POST
/orders
curl -X POST https://api.razorpay.com/v1/orders
-U [YOUR_KEY_ID]:[YOUR_KEY_SECRET]
-H 'content-type:application/json'
-d '{
"amount": 100,
"currency": "MYR",
"receipt": "qwsaq1",
"partial_payment": true,
"first_payment_min_amount": 230,
"notes": {
"key1": "value3",
"key2": "value2"
}
}'

Request Parameters

amount

mandatory

integer The amount to be paid by the customer in sen. For example, if the amount is MYR 500.00, enter 50000.

currency

mandatory

string The currency in which the payment should be made by the customer. Length must be of 3 characters.

receipt

optional

string Your receipt id for this order should be passed here. Maximum length is 40 characters.

notes

optional

json object Key-value pair that can be used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”.

partial_payment

optional

boolean Indicates whether the customer can make a partial payment. Possible values:

  • true: The customer can make partial payments.
  • false (default): The customer cannot make partial payments.

first_payment_min_amount

optional

integer Minimum amount that must be paid by the customer as the first partial payment. For example, if an amount of MYR 7,000.00 is to be received from the customer in two installments of #1 - MYR 5,000.00, #2 - MYR 2,000.00 then you can set this value as 500000. This parameter should be passed only if partial_payment is true.

Know more about

.

Response Parameters

Descriptions for the response parameters are present in the

parameters table.

Error Response Parameters

The error response parameters are available in the

.

Pass the Checkout options. Ensure that you pass the order_id that you received in the response of the previous step.

var options = {
"key": key,
"amount": 29935,
"order_id": "order_EMBFqjDHEEn80l", // Generate order_id using Orders API,
"card[cvv]": <CVV>,
"card[expiry_month]": 11,
"card[expiry_year]": 25,
"card[name]": "Test User",
"card[number]": "4111111111111111",
"contact": "9900990099",
"currency": "INR",
"email": "gaurav.kumar@example.com",
"description": "Fine T-Shirt",
"method": "card"
};
_razorpay.submit(options);

You must pass these parameters in Checkout to initiate the payment.

key

mandatory

string API Key ID generated from the Curlec Dashboard.

amount

mandatory

integer The amount to be paid by the customer in currency subunits. For example, if the amount is MYR 100.00, enter 10000.

currency

mandatory

string The currency in which the payment should be made by the customer.

description

optional

string Description of the product shown in the Checkout form. It must start with an alphanumeric character.

image

optional

string Link to an image (usually your business logo) shown in the Checkout form. Can also be a base64 string, if loading the image from a network is not desirable.

order_id

mandatory

string Order ID generated via the

.

notes

optional

object Set of key-value pairs that can be used to store additional information about the payment. It can hold a maximum of 15 key-value pairs, each 256 characters long (maximum).

method

mandatory

string The payment method used by the customer on Checkout.
Possible values:

  • card (default)
  • fpx (default)
  • wallet (default)

card

mandatory if method=card

object The details of the card that should be entered while making the payment.

number

integer Unformatted card number.

name

string The name of the cardholder.

expiry_month

integer Expiry month for card in MM format.

expiry_year

integer Expiry year for card in YY format.

cvv

integer CVV printed on the back of the card.

bank

mandatory if method=fpx

string Bank code. List of available banks enabled for your account can be fetched via

.

wallet

mandatory if method=wallet

string Wallet code for the wallet used for the payment. Possible values:

  • touchngo (default)
  • grabpay (default)

callback_url

optional

string Customers will be redirected to this URL on successful payment. Ensure that the domain of the Callback URL is whitelisted. This parameter is mandatory for FPX payments.

redirect

optional

boolean Determines whether to post a response to the event handler post payment completion or redirect to Callback URL. callback_url and redirect parameters are mandatory for FPX payments. Possible values:

  • true: Customer is redirected to the specified callback URL in case of payment failure. For FPX payments, the redirect parameter should always be sent as true.
  • false (default): Customer is not redirected to the specified callback URL.

Provide your customers with a better payment experience by enabling UPI Intent on your app's Checkout form. In the UPI Intent flow:

  1. Customer selects UPI as the payment method in your iOS app. A list of UPI apps supporting the intent flow is displayed. For example, PhonePe, Google Pay and Paytm.
  2. Customer selects the preferred app. The UPI app opens with pre-populated payment details.
  3. Customer enters their UPI PIN to complete their transactions.
  4. Once the payment is successful, the customer is redirected to your app or website.

To enable this in your iOS integration, you must make the following changes in your app's info.plist file.

<key>LSApplicationQueriesSchemes</key>
<array>
<string>tez</string>
<string>phonepe</string>
<string>paytmmp</string>
<string>credpay</string>
<string>mobikwik</string>
<string>freecharge</string>
<string>in.fampay.app</string>
<string>bhim</string>
<string>amazonpay</string>
<string>navi</string>
<string>kiwi</string>
<string>payzapp</string>
<string>jupiter</string>
<string>omnicard</string>
<string>icici</string>
<string>popclubapp</string>
<string>sbiyono</string>
<string>myjio</string>
<string>slice</string>
<string>bobupi</string>
<string>shriramone</string>
<string>indusmobile</string>
<string>whatsapp</string>
</array>

Know more about

.

Configure and initiate a recurring payment transaction on UPI Intent:

let options: [String:Any] = [
"key": "YOUR_KEY_ID",
"order_id": "order_DBJOWzybfXXXX",
"customer_id": "cust_BtQNqzmBlXXXX",
"prefill": [
"contact": "+919000090000",
"email": "gaurav.kumar@example.com"
],
"image": "https://spaceplace.nasa.gov/templates/featured/sun/sunburn300.png",
"amount": 10000, // Amount should match the order amount
"currency": "INR",
"recurring": 1 // This key value pair is mandatory for Intent Recurring Payment.
]

Use the below code to open the Razorpay checkout:

_razorpay.submit(options);

A successful payment returns the following fields to the Checkout form.

  • You need to store these fields in your server.
  • You can confirm the authenticity of these details by verifying the signature in the next step.

razorpay_payment_id

string Unique identifier for the payment returned by Checkout only for successful payments.

razorpay_order_id

string Unique identifier for the order returned by Checkout.

razorpay_signature

string Signature returned by the Checkout. This is used to verify the payment.

This is a mandatory step to confirm the authenticity of the details returned to the Checkout form for successful payments.

To verify the razorpay_signature returned to you by the Checkout form:

  1. Create a signature in your server using the following attributes:

    • order_id: Retrieve the order_id from your server. Do not use the razorpay_order_id returned by Checkout.
    • razorpay_payment_id: Returned by Checkout.
    • key_secret: Available in your server. The key_secret that was generated from the .
  2. Use the SHA256 algorithm, the razorpay_payment_id and the order_id to construct a HMAC hex digest as shown below:

    generated_signature = hmac_sha256(order_id + "|" + razorpay_payment_id, secret);
    if (generated_signature == razorpay_signature) {
    payment is successful
    }
  3. If the signature you generate on your server matches the razorpay_signature returned to you by the Checkout form, the payment received is from an authentic source.

Given below is the sample code for payment signature verification:

RazorpayClient razorpay = new RazorpayClient("[YOUR_KEY_ID]", "[YOUR_KEY_SECRET]");
String secret = "EnLs21M47BllR3X8PSFtjtbd";
JSONObject options = new JSONObject();
options.put("razorpay_order_id", "order_IEIaMR65cu6nz3");
options.put("razorpay_payment_id", "pay_IH4NVgf4Dreq1l");
options.put("razorpay_signature", "0d4e745a1838664ad6c9c9902212a32d627d68e917290b0ad5f08ff4561bc50f");
boolean status = Utils.verifyPaymentSignature(options, secret);

After you have completed the integration, you can

, make test payments, replace the test key with the live key and integrate with other .

If you use M1 MacBook, you need to make the following changes in your podfile.

Handy Tips

Add the following code inside post_install do |installer|.

installer.pods_project.build_configurations.each do |config|
config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
end

Handy Tips

On the Dashboard, ensure that the payment status is captured. Refer to the payment capture settings page to know how to

.

You can track the payment status in three ways:

To verify the payment status from the Dashboard:

  1. Log in to the and navigate to TransactionsPayments.
  2. Check if a Payment Id has been generated and note the status. In case of a successful payment, the status is marked as Captured.
Check if the payment id is generated and the status is captured


Is this integration guide useful?