Spreedly helps minimize PCI compliance scope and reduce development costs for platforms and merchants that work with multiple payment gateways and/or third party order processing API's. We do that via a universal credit card token that you store once but use anywhere. 

We want that story to remain the same as we add support for mobile platform payment services like Apple Pay. We now support the ability to use Apple Pay payments across compatible endpoints, without being locked into a single gateway. Here's how it works:

  • ‍You provision your Apple Pay certificate from Spreedly instead of any single gateway
  • ‍To execute a transaction, send the Apple Pay payment token to Spreedly along with the gateway you wish to execute against
  • ‍Spreedly decrypts the payment token using your Apple Pay certificate and passes the decrypted card number and cryptogram to the gateway, which processes the transaction.

Having Spreedly manage the Apple Pay decryption has several benefits including: 1) the flexibility to process against more than one gateway within the same iOS application, 2) the freedom to change gateways without re-provisioning your certificate and having to release an app update, and 3) the ability to execute against non-gateway payments APIs. 

The main requirement for Spreedly's Apple Pay support during this beta period is that the endpoint's API supports network tokenization (basically, that it accepts a card number and corresponding "cryptogram" which provides additional security and verification to the transaction). 

The introduction of Apple Pay has many providers  adding support for network tokenization so please contact us if your gateway or endpoint is not yet supported by Spreedly.

More from Our Blog

Recent Posts You Might Like

No items found.
See All Posts