To add Apple Pay and STC Pay, you usually do not connect to either one directly. You choose a payment gateway that supports both, set up Apple Pay in your Apple Developer account, enable STC Pay on your merchant account, and then use the gateway’s SDK or API. Your app collects the payment, and your backend confirms the result with the gateway.
The setup is mostly configuration. The mistakes come from certificates, missing payment networks, and trusting the app instead of the server. This guide covers both methods, step by step.
The two methods feel different to users, and they run differently under the hood.
| Apple Pay | STC Pay | |
| Type | Tokenized card payment on Apple devices | Digital wallet payment |
| User action | Taps the Apple Pay button, then confirms with Face ID, Touch ID, or passcode | Enters an STC Pay mobile number, then an SMS one-time code |
| Platforms | iPhone, iPad, Apple Watch, and Safari | Any app, through a gateway SDK or API |
| What you need | Apple Developer account, Merchant ID, payment processing certificate | STC Pay merchant account and merchant ID |
| Currency | Set by your merchant account | Saudi riyal (SAR) only |
| Confirmation | Encrypted token sent to your gateway | Gateway confirms after the code is verified |
Both usually settle through your payment gateway. That is why the first decision is the gateway.
Pick the gateway before you touch any code. Check these points:
Several gateways publish documentation for these methods. For example, Moyasar documents Apple Pay and STC Pay for iOS and Flutter. Checkout.com documents STC Pay for mobile apps through its Flow component. Amazon Payment Services documents STC Pay with a mobile SDK. Geidea and Noon Payments document Apple Pay with the mada network. Coverage changes, so confirm the current list before you commit.
Some gateways let you manage the Apple Pay payment processing certificate on their side. Others let you manage it on your own backend. The second route puts you in a higher PCI DSS scope. For most apps, the gateway-managed route is simpler and safer.
Follow this order on iOS.
Our custom iOS app development team follows this order on every Apple Pay project.
Here is a minimal Swift example for Saudi Arabia:
let request = PKPaymentRequest()
request.merchantIdentifier = “merchant.com.yourcompany.app”
request.countryCode = “SA”
request.currencyCode = “SAR”
request.supportedNetworks = [.visa, .masterCard, .mada]
request.merchantCapabilities = .threeDSecure
request.paymentSummaryItems = [
PKPaymentSummaryItem(
label: “Order 1234”,
amount: NSDecimalNumber(string: “99.00”)
)
]
Do not forget .mada in the supported networks. Gateway documentation states that you must include it to accept Mada cards. Without it, many Saudi cards will not appear in the payment sheet.
STC Pay works the same way on both platforms. The user enters a phone number, receives a one-time code by SMS, and confirms it.
Most gateway SDKs include a ready-made STC Pay view that handles the phone number and code steps. Use it first. Build a custom screen only when your design needs it.
Apple Pay does not run in Android apps. Apple Pay works on Apple devices. For Android users, offer these options instead:
If you build with Flutter or React Native, you can share most of the checkout logic across both platforms. You still configure Apple Pay only on iOS. Our Android app development team builds Google Pay and wallet flows alongside the iOS checkout so both platforms launch together.
The app collects the payment, but the backend decides what is true.
A correct integration can still lose sales if checkout feels unclear.
Payments and Arabic localization also shape your budget. We explain how in our guide to mobile app development cost in Saudi Arabia.
Apple treats digital goods differently from physical goods and services. Digital content and subscriptions used inside the app generally use Apple’s in-app purchase. Physical goods and services that users consume outside the app, such as deliveries, bookings, and retail orders, can use Apple Pay and other payment methods. Check the current guidelines for your exact product before you design checkout.
Run these checks in the gateway sandbox, then with small live payments.
Gateway fees, onboarding time, and settlement terms differ by provider, and no single public price applies. Ask each gateway for fees and onboarding steps in writing. Add development time for the checkout screens, backend, webhooks, and testing.
Planning payments early also helps the whole build. Our team of mobile app development in Saudi Arabia scopes payments during discovery, so certificates, merchant accounts, and approvals start before the checkout screens are ready.
To add Apple Pay and STC Pay cleanly, start with the gateway, finish the account setup early, and keep the server in charge of payment truth. Apple Pay gives iPhone users a fast, secure tap. STC Pay gives wallet users a familiar code-based flow. Together, they cover many Saudi shoppers.
Teams that plan certificates, merchant IDs, and webhooks in the first sprint avoid the long delays at the end. The integration code is small. The setup around it is what takes time.
In most cases, yes. A gateway receives the Apple Pay token or confirms the STC Pay code, then settles the money to you. Most apps use a gateway that supports both methods.
Yes, when your gateway and your payment request support the MADA network. Include the MADA network in your supported networks list.
No. Apple Pay works on Apple devices. Offer Google Pay, STC Pay, and card payments to Android users.
The user enters an STC Pay mobile number, receives a one-time code by SMS, and enters it in your app. The gateway verifies the code and confirms the payment.
Gateway documentation states that STC Pay supports Saudi riyal transactions only.
Digital content and subscriptions inside an iOS app generally need Apple’s in-app purchase. Apple Pay fits physical goods and services. Check the current App Store guidelines for your case.
Card data security rules still apply. Using a gateway-managed flow keeps raw card data away from your servers and reduces your scope. Confirm your obligations with your gateway and compliance team.
Technical details come from public documentation from Apple and from payment gateways including Moyasar, Checkout.com, Amazon Payment Services, Geidea, and Noon Payments. Gateways and Apple update their requirements often, so confirm the latest steps in your own accounts before you build.
We set up gateways, certificates, and checkout flows for iOS and Android. Talk to our team and we will scope Apple Pay and STC Pay before you commit to a build.