Integrate the Cashfree Payment Gateway iOS SDK to embed a WebView-based payment checkout in your iOS app, supporting deployment targets from iOS 11 onwards.
Cashfree’s iOS SDK provides a streamlined payment solution that integrates the payment gateway into your iOS applications through a WebView-based checkout implementation, supporting iOS deployment target 11 and above.
To integrate the Cashfree Payment Gateway, you must first create an order. Complete this step before you process any payments. Configure an endpoint on your server to handle order creation. You can’t call this API from the client-side.
Create orders through your server as this API requires your secret key. Don’t call it directly from your mobile application.
API request for creating an order
Here’s a sample request for creating an order using your desired backend language. Cashfree offers backend SDKs to simplify the integration process.
import { Cashfree, CFEnvironment } from "cashfree-pg";const cashfree = new Cashfree( CFEnvironment.PRODUCTION, "{Client ID}", "{Client Secret Key}");function createOrder() { var request = { order_amount: "1", order_currency: "INR", customer_details: { customer_id: "node_sdk_test", customer_name: "", customer_email: "example@gmail.com", customer_phone: "9999999999", }, order_meta: { return_url: "https://test.cashfree.com/pgappsdemos/return.php?order_id=order_123", }, order_note: "", }; cashfree .PGCreateOrder(request) .then((response) => { var a = response.data; console.log(a); }) .catch((error) => { console.error("Error setting up order request:", error.response.data); });}
After successfully creating an order, you will receive a unique order_id and payment_session_id that you need for subsequent steps.You can view all the complete API request and response for /ordershere.
Web Checkout is a streamlined payment solution that integrates Cashfree’s payment gateway into your iOS app through the SDK. This implementation uses a WebView to provide a secure, feature-rich payment experience.Your customers are presented with a familiar web interface where they can enter their payment details and complete their transaction seamlessly. All payment logic, UI components, and security measures are managed by the SDK, eliminating the need for complex custom implementation.
The recommended way to integrate the Cashfree iOS SDK is by using Swift Package Manager. You can do this through the Xcode interface.To add the Cashfree iOS SDK to your project, follow these steps:
This object contains essential information about the order, including the payment session ID (payment_session_id) and order ID (order_id) obtained from Step 1. It also specifies the environment (sandbox or production).
do { let session = try CFSession.CFSessionBuilder() .setOrderID(order_id) .setPaymentSessionId(payment_session_id) .setEnvironment(Utils.environment) .build() return session;} catch let e { let error = e as! CashfreeError self.createAlert(title: "Warning", message: error.localizedDescription)}
Set up callback handlers to handle events after payment processing. The callback implements CFResponseDelegate to handle payment responses and errors. Initialise it in viewDidLoad by calling CFPaymentGatewayService.getInstance().setCallback(self).
onError: Handles payment failures by displaying an alert with error details
verifyPayment: Called when payment needs merchant verification, shows status alert to user
Make sure to set the callback at activity’s onCreate as this also handles the activity restart cases.
extension ViewController: CFResponseDelegate { func onError(_ error: CFErrorResponse, order_id: String) { self.createAlert(title: error.status ?? "ERROR", message: error.message ?? "error_message_not_present") } func verifyPayment(order_id: String) { self.createAlert(title: "VERIFY PAYMENT", message: "Payment has to be verified by merchant for \(order_id)") }}// Class Variablelet pgService = CFPaymentGatewayService.getInstance()override func viewDidLoad() { super.viewDidLoad() pgService.setCallback(self) }
After the customer completes the payment, you must confirm the payment status. Once the payment finishes, the user redirects back to your activity.To verify an order you can call our /pg/orders endpoint from your backend. You can also use our SDK to achieve the same.
Always verify the order status before you deliver services to the customer. You can use the Get Order API for this. An order is successful when the order_status is PAID.
To confirm the error returned in your iOS application, you can view the error codes that are exposed by the SDK.
Show error codes
CashfreeError is an Enum that inherits Foundations Error class. The following are some of the error codes that are exposed by the SDK:
Error codes
Message
MISSING_CALLBACK
The callback is missing in the request.
ORDER_ID_MISSING
The “order_id” is missing in the request.
CARD_EMI_TENURE_MISSING
The “emi_tenure” is missing or invalid (It has to be greater than 0).
INVALID_UPI_APP_ID_SENT
The id sent is invalid. The value has to be one of the following: “tez://”,“phonepe://”,“paytmmp://”,“bhim://. Please refer the note in CFUPI class for more details
INVALID_PAYMENT_OBJECT_SENT
The payment object that is set does not match any payment mode. Please set the correct payment mode and try again.
WALLET_OBJECT_MISSING
The CFWallet object is missing in the request
NETBANKING_OBJECT_MISSING
The CFNetbanking object is missing in the request.
UPI_OBJECT_MISSING
The CFUPI object is missing in the request.
CARD_OBJECT_MISSING
The CFCard object is missing in the request.
INVALID_WEB_DATA
The url seems to be corrupt. Please reinstantiate the order.
SESSION_OBJECT_MISSING
The “session” is missing in the request
PAYMENT_OBJECT_MISSING
The “payment” is missing in the request
ENVIRONMENT_MISSING
The “environment” is missing in the request.
ORDER_TOKEN_MISSING
The “order_token” is missing in the request.
CHANNEL_MISSING
The “channel” is missing in the request.
CARD_NUMBER_MISSING
The “card_number” is missing in the request.
CARD_EXPIRY_MONTH_MISSING
The “card_expiry_mm” is missing in the request.
CARD_EXPIRY_YEAR_MISSING
The “card_expiry_yy” is missing in the request.
CARD_CVV_MISSING
The “card_cvv” is missing in the request.
UPI_ID_MISSING
The “upi_id” is missing in the request
WALLET_CHANNEL_MISSING
The “channel” is missing in the wallet payment request
WALLET_PHONE_MISSING
The “phone number” is missing in the wallet payment request
NB_BANK_CODE_MISSING
The “bank_code” is missing in the request
Affiliate partner program
As a developer building payment experiences for your clients, you can earn additional income while providing them with industry-leading payment solutions.