Flutter SDK

Flutter is an open-source SDK. It is used by developers to develop solutions for different operating systems and the web from a single codebase.

The Cashfree Flutter SDK allows you to integrate Cashfree Payment Gateway with your application and start collecting payments from your customers. It opens the payment page in a webview. The Cashfree SDK has been designed to minimise the complexity of handling and integrating payments in your Flutter project.

The Cashfree Flutter SDK is available here.

Integration Steps

To integrate Cashfree SDK with your Flutter application.

  1. Initiate Payment - Invoke a payment API from the Cashfree SDK with the token generated when the customer initiates payment for an order from your application. Cashfree SDK displays appropriate screens to the customer for the payment.

  2. Receive and handle response - Cashfree SDK returns a response after the payment flow is complete.

  3. Verify response - We recommend you to verify the payment response using webhooks and by checking the signature value returned in the payment response.

Step 1: Create an account with Cashfree and get the API Keys.

  1. Go to Cashfree website and create an account. Click here for detailed steps on how to create and activate your account.

  2. Login to your Merchant Dashboard using the same credentials.

  3. In the Payment Gateway section click View Dashboard > Credentials. For security purposes, you need to enter your password for verification.

  4. Copy the app ID and the secret key. These values are required to create the order token from your server. Order tokens are used to authenticate the API calls made from Cashfree Flutter SDK.

Step 2: Integrate Cashfree SDK in your application

To integrate the SDK, follow the steps below:

Step 2a: Add Dependency

Open the pubspec.yaml file located inside the app folder, and add cashfree_pg: under dependencies.

cashfree_pg: 0.0.3+5

Step 2b: Add permissions (Android)

The Cashfree PG SDK requires that you add the INTERNET permission in your Android Manifest file.

<manifest ...>
<uses-permission android:name="android.permission.INTERNET" />
<application ...>

Step 3: Generate Token (From Backend)

The cftoken is used to authenticate the payment requests made from SDK. It has to be generated for every payment attempt made for an order. Pass this token to the SDK while initiating the payment for that order. For generating a cftoken you need to use our token generation API.

Ensure that this API is called only from your backend as it uses a secret key. This API should never be called from the App.

Request Description to Generate Token

Production - set the URL tohttps://api.cashfree.com/api/v2/cftoken/order

Testing - set the URL to https://test.cashfree.com/api/v2/cftoken/order

You need to send orderId, orderCurrency and orderAmount as a JSON object to the API endpoint and in response, you will receive a token. See the description of the request below.

curl -XPOST -H 'Content-Type: application/json'
-H 'x-client-id: <YOUR_APP_ID>'
-H 'x-client-secret: <YOUR_SECRET_KEY>'
-d '{
"orderId": "<ORDER_ID>",
"orderAmount":<ORDER_AMOUNT>,
"orderCurrency": "<ORDER_CURRENCY>"
}' '<TEST_OR_PROD_API_URL>’'

Request Example: Replace YOUR_APP_ID and YOUR_SECRET_KEY with actual values.

curl -XPOST -H 'Content-Type: application/json' -H 'x-client-id: 7051d9675fae9ae886f9de1b1507' -H 'x-client-secret: 90c0919f5f4b31a06eb8ba3042f57272166ccdfb' -d '{
"orderId": "Order0001",
"orderAmount":1,
"orderCurrency":"INR"
}' 'https://test.cashfree.com/api/v2/cftoken/order'

Response Example

{
"status": "OK",
"message": "Token generated",
"cftoken": "v79JCN4MzUIJiOicGbhJCLiQ1VKJiOiAXe0Jye.s79BTM0AjNwUDN1EjOiAHelJCLiIlTJJiOik3YuVmcyV3QyVGZy9mIsEjOiQnb19WbBJXZkJ3biwiIxADMwIXZkJ3TiojIklkclRmcvJye.K3NKICVS5DcEzXm2VQUO_ZagtWMIKKXzYOqPZ4x0r2P_N3-PRu2mowm-8UXoyqAgsG"
}

The "cftoken" is used to authenticate your payment request.

Step 4: Initiate Payment

To initiate payments, your application passes the order info and the cftoken to the SDK. The relevant payment screen is displayed to the customer where they enter the required information and make the payment. Flutter SDK verifies the payment after it is complete and sends a response to the application. The application handles the response appropriately.

The order details passed during the token generation and the payment initiation should match. Else, you will get an `Invalid order details` error.

Wrong appId and token will result in `Unable to authenticate merchant` error. The token generated for payment is valid for 5 minutes within which the payment has to be initiated. Else, you will get an `Invalid token` error.

Step 5. Receive and Handle Response

When you invoke the SDK function, it returns Future as response.

Step 6. Verify Response

We recommend you to verify the payment response using webhooks. You can also verify the response by checking the signature in the payment response.

Web Checkout

Web Checkout is the standard flow for Cashfree Flutter SDK. In this flow, the SDK loads a webview which renders the payment page. The customer can fill the required payment details here to complete the payment. The Web Checkout can be used in two ways:

  1. Web Checkout using Cashfree UI: Customer selects the payment mode and enters the payment details within the Cashfree's web payment page to complete the payment.

  2. Seamless Web Checkout: Customer selects the payment mode and enters payment details in your application. These details are then passed on to the Cashfree SDK. Webview is launched only for two-factor authentication.

For both the modes you need to invoke the doPayment() method. However, there are a few additional parameters you need to pass for seamless integration.

Web Checkout using Cashfree UI

Here, you can use our prebuilt Cashfree UI to accept payments. For both Web Checkout and Seamless Web Checkout you need to invoke the doPayment() method. However, there are a few extra parameters you need to pass for seamless integration method.

doPayment

Future<Map<dynamic, dynamic>> doPayment(Map<String, dynamic> inputs)

Initiates the payment in a webview. The customer will be taken to the payment page on the cashfree server where they will have the option to pay through any payment option that is activated on their account. Once the payment is done the webview will close and the response will be delivered in the callback.

Parameters:

Seamless Web Checkout

When your business requires a customised payment flow, you can use the seamless integration method. You can implement the payment page as per your requirement and then use our SDK to authorise the payment. Once the payment details are collected the OTP or the two-factor authentication page will open in a webview. After the payment is confirmed the webview closes and you will receive a response.

We recommend that you use Web Checkout using Cashfree UI integration unless you are certain that you require a customised payment flow.

The following sections describe the additional parameters for each of the payment methods:

Credit/Debit Card

Add these following parameters to the params map before invoking doPayment() method to initiate a seamless card transaction.

inputs[ "paymentOption"] = “card”;
inputs[ "card_number"] = “4434260000000008”; //Replace Card number
inputs[ "card_expiryMonth"] = “05”; // Card Expiry Month in MM
inputs[ "card_expiryYear"] = “2021”; // Card Expiry Year in YYYY
inputs[ "card_holder"] = “John Doe”; // Card Holder name
inputs[ "card_cvv"] = “123”; // Card CVV

Net Banking

Add the following parameters to the params map before invoking doPayment() method to initiate a seamless net banking transaction. All valid bank codes are available here.

inputs[ "paymentOption"] = “nb”;
inputs[ "paymentCode"] = “3333”; // Put correct bank code here

Wallet

Add the following parameters to the params map before invoking doPayment() method to initiate a seamless wallet transaction. All valid wallet codes are available here.

inputs[ "paymentOption"] = “wallet”;
inputs[ "paymentCode"] = “4001”; // Put correct wallet code here

UPI

Add the following parameters to the params map before invoking doPayment() method to initiate a seamless UPI transaction.

inputs[ "paymentOption"] = “upi”;
inputs[ "upi_vpa"] = “testsuccess@gocash”; // Put correct upi vpa here

Paypal

Add the following parameters to the params map before invoking doPayment() method to initiate a seamless Paypal transaction.

inputs[ "paymentOption"] = "paypal";

Sample Code

//Replace with actual values
String stage = "TEST";
String orderId = "Order Id";
String orderAmount = "ORDER AMOUNT";
String tokenData = "TOKEN_DATA";
String customerName = "Customer Name";
String orderNote = "Order Note";
String orderCurrency = "INR";
String appId = "APP_ID";
String customerPhone = "9999999999";
String customerEmail = "sample@gmail.com";
String notifyUrl = "https://test.gocashfree.com/notify";
Map<String, dynamic> inputParams = {
"orderId": orderId,
"orderAmount": orderAmount,
"customerName": customerName,
"orderNote": orderNote,
"orderCurrency": orderCurrency,
"appId": appId,
"customerPhone": customerPhone,
"customerEmail": customerEmail,
"stage": stage,
"notifyUrl": notifyUrl
};
CashfreePGSDK.doPayment(inputParams)
.then((value) => value?.forEach((key, value) {
print("$key : $value");
//Do something with the result
}));
}

Verify Response

It is recommended to verify the payment response from the SDK using one of the following methods.

Webhook Notifications

We send a notification from Cashfree backend to your backend whenever a payment is successful for an order. This is useful for users in cases when the internet connection is not stable after payment. This will allow you to reconcile all the successful orders at your end. The notification will be sent to notifyUrl which is specified during order creation. The parameters sent in notification are described here.

To specify notifyUrl, add it with other parameters (orderId, orderAmount etc.) as shown below:

inputs[ "notifyUrl"] = “https://example.com/path/to/notify/url/”;

Notifications are usually instant but rarely can take a minute to hit your server. Make sure that your url supports https. Notifications are sent only in the case of successful payments. Sometimes you may receive the same notification two or more times. It is recommended to ensure that your implementation of the webhook is idempotent. Ensure that you verify the signature in the webhook response.

Verify Signature

Verify the signature value in the payment response to check the authenticity of the transaction response. In every response, we add a digital signature to establish the authenticity of the message. We require you to verify this received signature at your end. This will verify if the response has tampered. This verification has to be done on your server as it will involve secretKey which should not be exposed on the client side.

PHP
PYTHON
JAVA
CSHARP
PHP
<?php
$orderId = $_POST["orderId"];
$orderAmount = $_POST["orderAmount"];
$referenceId = $_POST["referenceId"];
$txStatus = $_POST["txStatus"];
$paymentMode = $_POST["paymentMode"];
$txMsg = $_POST["txMsg"];
$txTime = $_POST["txTime"];
$signature = $_POST["signature"];
$data = $orderId.$orderAmount.$referenceId.$txStatus.$paymentMode.$txMsg.$txTime;
$hash_hmac = hash_hmac('sha256', $data, $secretkey, true) ;
$computedSignature = base64_encode($hash_hmac);
if ($signature == $computedSignature) {
// Proceed
} else {
// Reject this call
}
?>
PYTHON
iimport hashlib
import hmac
import base64
@app.route('/notify_url/', methods=["POST"])
def notify_url_process():
postData = {
"orderId" : request.form['orderId'],
"orderAmount" : request.form['orderAmount'],
"referenceId" : request.form['referenceId'],
"txStatus" : request.form['txStatus'],
"paymentMode" : request.form['paymentMode'],
"txMsg" : request.form['txMsg'],
"txTime" : request.form['txTime'],
}
signatureData = postData["orderId"] + postData["orderAmount"] + postData["referenceId"] + postData["txStatus"] + postData["paymentMode"] + postData["txMsg"] + postData["txTime"]
message = bytes(signatureData).encode('utf-8')
#get secret key from your config
secret = bytes(secretKey).encode('utf-8')
signature = base64.b64encode(hmac.new(secret,
message,digestmod=hashlib.sha256).digest())
JAVA
LinkedHashMap<String, String> postData = new LinkedHashMap<String, String>();
postData.put("orderId", ORDERID);
postData.put("orderAmount", ORDERAMOUNT);
postData.put("referenceId", REFERENCE_ID);
postData.put("txStatus", TXN_STATUS);
postData.put("paymentMode", PAYMENT_MODE);
postData.put("txMsg", TX_MSG);
postData.put("txTime", TX_TIME);
String data = "";
Set<String> keys = postData.keySet();
for (String key : keys) {
data = data + postData.get(key);
}
String secretKey = "" // Get secret key from config;
Mac sha256_HMAC = Mac.getInstance("HmacSHA256");
SecretKeySpec secret_key_spec = new
SecretKeySpec(secretKey.getBytes(),"HmacSHA256");
sha256_HMAC.init(secret_key_spec);
String signature = Base64.getEncoder().encodeToString(sha256_HMAC.doFinal(data.getBytes()));
CSHARP
using System;
using System.Security.Cryptography;
using System.Collections.Generic;
namespace Rextester {
public class Program {
private string CreateToken(string message, string secret){
secret = secret ?? "";
var encoding = new System.Text.ASCIIEncoding();
byte[] keyByte = encoding.GetBytes(secret);
byte[] messageBytes = encoding.GetBytes(message);
using (var hmacsha256 = new HMACSHA256(keyByte))
{
byte[] hashmessage = hmacsha256.ComputeHash(messageBytes);
return Convert.ToBase64String(hashmessage);
}
}
public static void Main(string[] args) {
string secret = "<your_secret_key>";
string data = "";
data = data + "FEX101";
data = data + "10.00";
data = data + "19992";
data = data + "SUCCESS";
data = data + "pg";
data = data + "payment done";
data = data + "2018-02-02 17:29:12";
Program n = new Program();
string signature = n.CreateToken(data, secret);
Console.WriteLine(signature);
}
}
}

Request and Response Parameters

Request Parameter

Parameter

Required

Description

stage

Yes

Environment - TEST or PROD

appId

Yes

Your app id

orderId

Yes

Order/Invoice Id

orderAmount

Yes

Bill amount of the order

orderNote

No

A help text to make customers know more about the order

orderCurrency

Yes

Currency code of the order. Default is INR.

customerName

No

Name of the customer

customerPhone

Yes

Phone number of customer

customerEmail

Yes

Email ID of the customer

tokenData

Yes

Token generated here

notifyUrl

No

Notification URL for server-server communication. Useful when a user's connection drops after completing payment.

paymentModes

No

Allowed payment modes for this order. Available values: cc, dc, nb, paypal, upi, wallet. Leave it blank if you want to display all modes.

Response parameters

These parameters contain the details of the transaction.

Parameter

Description

orderId

Order id for which transaction has been processed. Ex: GZ-212

orderAmount

Amount of the order. Ex: 256.00

paymentMode

Payment mode of the transaction.

referenceId

Cashfree generated unique transaction Id. Ex: 140388038803

txStatus

Payment status for that order. Values can be : SUCCESS, FLAGGED, PENDING, FAILED, CANCELLED.

paymentMode

Payment mode used by customers to make the payment. Ex: DEBIT_CARD, MobiKwik, etc

txMsg

Message related to the transaction. Will have the reason, if payment failed

txTime

Time of the transaction

type

Fixed value : CashFreeResponse. To identify the response is from cashfree SDK.

signature

Response signature

  • There can be scenarios where the SDK is not able to verify the payment within a short period of time. The status of such orders will be PENDING.

  • If the Webview closes immediately after it is opened then it could be because of some issues with the input that is passed to the SDK. Check the inputs passed and if you still need further help reach out to us at techsupport@cashfree.com.

  • If you are getting INCOMPLETE as the transaction status please reach out to your account manager or techsupport@cashfree.com.

Checklist

Checklist to Go Live

  • Ensure you are triggering https://api.cashfree.com/api/v2/cftoken/orderendpoint for generating token.

  • Pass the Production appId/secretKey in the x-client-id and x-client-secret of the token request API. Obtain these appId/secretKey here in the Production section.

  • When calling doPayment() ensure that the stage parameter is PROD.

  • When calling doPayment() the params map is sent to your appId. Ensure it is the correct production appId.

Checklist to Revert to Test

  • Ensure you are triggering https://test.cashfree.com/api/v2/cftoken/orderendpoint for generating Token

  • Pass the Test appId/secretKey in the x-client-id and x-client-secret of the token request API. Obtain these appId/secretKey here in the Sandbox section.

  • When calling doPayment() ensure that the stage parameter is TEST.

  • When calling doPayment() the params map is sent to your appId. Ensure it is the correct test appId.