Paytabs provides you with multiple methods for using ApplePay, for easy-to-use integration, and even more easy implementation for developers. 


ApplePay Payment Workflow


The ApplePay "Pay" button would trigger the ApplePay wallet to be opened in a popup screen (Only via any Apple Devices). This will lead the customer to choose one of his saved cards to proceed with the payment using the token sent from the merchant side to the PayTabs side.


How is this done?


The previous ApplePay payment workflow can be performed through several ways, as clarified below:


Web Applications (via the PayTabs API endpoints)


In any Web Application, the ApplePay "Pay" button would trigger the ApplePay wallet to be opened in a popup screen (Only via the Safari browser on any Apple Device). This will lead the customer to choose one of his saved cards to proceed with the payment using the "apple_pay_token", which would be sent to the merchant's server-side, which would make the payment request to PayTabs side, as clarified in our ApplePay Payment Request solution article.


You should know that according to the mentioned solution article, the payment request doesn't include any card details; instead, it has the received "apple_pay_token".


To perform this step properly, you will need to configure your own ApplePay Certification first on your PayTabs dashboard, to know more about this please check our How to configure Apple Pay Certificate in my PayTabs dashboard? solution article.


To know how to get this token, kindly navigate to Apple Developers, to get a better understanding.




PayTabs Payment Page


By redirecting your customer to the PayTabs Payment Page (Only via the Safari browser on any Apple Device), means that you are creating your payment via our Hosted Payment Page via PayTabs' plugins or even the PayLinks or Invoices via PayTabs' dashboard. This will lead that the payment method will be completely managed and handled by our PayTabs, you don't have to worry about that.




Mobile Applications


  • Using PayTabs SDKs


    In any Mobile Application that is ONLY implemented using one of our SDKs, the same workflow as on (Web Applications) will be completely managed and handled by our SDKs, as clarified in our ApplePay Payment Request solution article (native IOS SDK).
    To perform this step properly, you will need to configure your own ApplePay Certification first on your PayTabs dashboard, to know more about this please check our How to configure Apple Pay Certificate in my PayTabs dashboard? solution article



  • Using the APIs endpoints


    In any Web Application, the ApplePay "Pay" button would trigger the ApplePay wallet to be opened in a popup screen (Only via the Safari browser on any Apple Device). This will lead the customer to choose one of his saved cards to proceed with the payment using the "apple_pay_token", which would be sent to the merchant's server-side, which would make the payment request to PayTabs side, as clarified in our ApplePay Payment Request solution article.

    You should know that according to the mentioned solution article, the payment request doesn't include any card details; instead, it has the received "apple_pay_token".

    To perform this step properly, you will need to configure your own ApplePay Certification first on your PayTabs dashboard, to know more about this please check our How to configure Apple Pay Certificate in my PayTabs dashboard? solution article



    To know how to get this token, kindly navigate to Apple Developers, to get a better understanding.


ApplePay Payment Method Limitations


  • ApplePay end-user (client) requirements.
  • It ONLY works on Apple Devices (Mac, iPhone, AppleWatch, ...etc).
  • It ONLY works on the Safari web browser.
  • iFrame mode is NOT supported by ApplePay.
  • Although ApplePay supports WebViews, the framework, language, plugin, or/and package that will be used to create the WebView should support ApplePay as well.
  • ApplePay is NOT supported in PayTabs test profiles.