Mobile SDKs

1

Create a payment intention

Every SDK payment starts from your backend by calling the Intention Creation API.

This step is responsible for:

• Defining the amount and currency
• Selecting the allowed payment methods
• Linking the payment to your internal order or reference ID

The response includes an intention reference (client secret) that will be passed to the Mobile SDK.

2

Initialize the Mobile SDK

In your mobile app (iOS or Android), you initialize the Paymob Mobile SDK using the intention reference received from your backend.

At this stage:

• The SDK is configured with the payment intention
• No sensitive payment data is handled by your app

This keeps your mobile application outside the PCI scope.

3

Present the native checkout UI

Once initialized, the SDK presents Paymob’s native checkout UI within your app, where the customer will complete the payment. The checkout experience follows the platform’s native look and feel, while Paymob handles input validation, security, and any required authentication (such as 3D Secure) seamlessly.

5

Callbacks and SDK result handling

After the payment is processed, Paymob sends callbacks to your backend with the final payment result and returns a status to the mobile app via the SDK callback.

• Backend callbacks must be used to confirm the final payment status, update orders, and trigger business actions. They are the source of truth.
• SDK callbacks should be used only to update the UI and show success or failure messages.

6

Callback security (HMAC)

Each callback can be authenticated using HMAC verification to ensure it was sent by Paymob and was not altered. Always verify callbacks before trusting their data