The steps to integrate iOS PG SDK on the native iOS App. [1. PreRequisites](🔗) [2. iOS PG SDK setup](🔗) [3. iOS PG App Side Implementation](🔗) [4. iOS PG Server Side Implementation](🔗)

### 1. PreRequisites

  1. XCode 12.5 or newer

  2. Cocoapod

  3. Onboarded on PhonePe as a Merchant (Given a MerchantID, & Saltkeys to generate the checksum on your servers)

  4. PhonePeAppId (Mandatory to pass in SDK initialisation)

### 2. iOS PG SDK setup

The ** PhonePePayment** framework is needed for the SDK to work for both PreProd (Testing) and Production (Deployment) environments.

##### Step 1. The **PhonePePayment** SDK is available through CocoaPods \[Refer to this [link](🔗) ]

Latest Phonepe iOS SDK Version: 2.5.1

<!--

PhonePeAppId (Refer [App Side - Step 2](🔗)) 2.4.1 - Merchant Needed to add it into info.plist.

iOS - PreProd App

Download the PhonePe iOS app for test environment **v5.8.50.1004-PREPROD** - [**here**](🔗)

\\

-->

##### Step 2. Installation

To install it, simply add the following line to your Podfile:



then run


##### Step 3. Import the framework in your project using **"import PhonePePayment"**

Remove the "DirectPaymentSDK" from your project if you have already integrated and wanted to migrate to CocoaPods.

### 3. iOS PG App Side Implementation

##### Step 1. In your Info.plist, create or append a new Array type node **LSApplicationQueriesSchemes** to append the following values:




##### Step 2. Update PhonePe App Id

Pass the PhonePe App ID value in the init method using the key: **appId**. Refer to [Step 5](🔗)

<!--

Add **PhonePeAppId** key with value as string in your app’s Info.plist as shown in the below screenshot for analytics purposes.

**To Get AppId**

Share the Apple Team Id with the PhonePe Integration team to generate the AppId to be used.



-->

##### Step 3. Create DeepLink Schema

Create a URLType for your app (Deeplink), if not already present. For example, we have used: **iOSIntentIntegration**. (You can create your own identifier for your app)



URLScheme should match the below conditions

  • Only Alphabets (lower and upper case) and numbers are allowed.

  • We can allow special characters only like dot and Hyphen

  • The name should always start with alphabets.

The schema should be correct to redirect the app otherwise it will not redirect back to the merchant app.

##### Step 4. Create DPSTransactionRequest Object

Using the Payload from your server, create a DPSTransactionRequest object, with callbackURL as the URLType created in the step above. Example: **callBackURL : iOSIntentIntegration**

##### Step 5. Initialize the PG SDK

Initialize the PhonePeDPSDK and pass the DPSTransactionRequest object to the SDK. After the payment is complete and a callback is received back to your app on the completionHandler, check the status of the transaction with your backend.



To Enable Debug Logs

Update the **PhonePeDPSDK.enableDebugLogs = true** or **enableLogging** flag to **true** in startPG method.

##### Step 6. Setup the Environment

Set the environment as **.uat_simulation** to test in the UAT Simulator environment. While moving to Production, set the environment as **.production**.

##### Step 7. In your AppDelegate, check for a callback from the PhonePe app and if found, pass it to the SDK.


### 4. iOS PG Server Side Implementation

##### Step 1. Save the below-assigned value on your server

##### Step 2. Construct the request body and encode it in Base 64 at your server as follows:


##### Step 3. Checksum Calculation

Select one of the salts shared with you and note its index. Construct the X-verify at your server as follows:


##### Step 4. Check the payment status

Once the payment is completed, please call the Check Transaction Status API to validate the response received via the App. You can call the Check Transaction Status at regular intervals to fetch the response from the PhonePe server in case a response is not received in the application even after 10 minutes of initiating the application.

##### Step 5. Handling Payment Status

The payment status can be Successful, Failed, Pending or any of the codes. For Pending, you should retry until the status changes to Successful or Failed.