Accept payments on your iOS apps: Our mobile SDKs support your entire payment and registration process and simplify the integration of any payment method in your mobile apps. Completely outsource your payment processes to us from inside your native apps. We also take care of redirecting your users to 3D Secure processes and enable smooth app-switches to other payment applications including Twint and PostFinance.
Easy Integration: Integrate many of our payment methods easily to your iOS projects. Smart, modern and secure UI components to master online payments in your apps.
Card Scanner: Let your customers scan their card information easily with our prebuilt card scanner. No time wasted with entering card information.
3DS 2.0 / SCA Ready: The iOS SDK takes over the complexity of the 3DS process. We remain in charge of redirecting users whenever a 3D authorization is required to the 3DS process of their bank and back to the SDK.
Smooth App-Switch: Do you offer payment methods like Twint or PayPal that require the user to confirm the payment in a separate mobile app? The library switches smoothly to external apps and back to the SDK.
Saved Payment Methods and Fast Checkouts: Save your customers' payment information for later use and offer fast checkouts in your app. Delegate the saved payment method selection to the library.
Theme Support: Style various items according to your corporate identity if needed. We also support the iOS dark theme.
Get started with our integration guide and the API reference.
The Datatrans iOS SDK requires Xcode 12 or later and is compatible with apps targeting iOS 11 or above.
link |
Stars: 8 |
Last commit: 6 days ago |
We just added better support for network tokenizations with American Express, relevant for PCI Proxy merchants. Starting 3.6.0, we also updated the Twint logic to support any Twint application. If you process Twint transactions, please read the breaking note below and update to the latest build asap.
With the introduction of iOS 15, Apple has imposed a limitation on the Info.plist file within iOS applications, restricting the number of app query scheme entries to a maximum of 50. Any entry beyond this limit will not function, irrespective of the order or sequence of queries. To enable app switch support for newer Twint applications, a renaming of the schemes defined in the array LSApplicationQueriesSchemes
in Info.plist is required.
As the number of Twint banking apps has now exceeded 40, we have introduced a new query mechanism to accommodate more apps while limiting Twint-related entries to 40.
Modifications to your Info.plist file:
twint-extended
along with twint-issuer1
, twint-issuer2
, up to twint-issuer39
.twint-issuer40
and higher.LSApplicationQueriesSchemes
entries in Info.plist.If you have limited space due to other integrations, use the SDK option twintMaxIssuerNumber
. Set this value to match your highest twint-issuerXY
scheme. For example, if Info.plist contains up to twint-issuer35
, set the SDK option twintMaxIssuerNumber
to 35
. Make sure the twint-extended
scheme is always included in your Info.plist file.
Important: Whenever possible, allocate the full 40 Twint schemes within LSApplicationQueriesSchemes
. This ensures the best possible user experience, allowing for seamless app switching during payments.
discountAmount
)LSApplicationQueriesSchemes
& schemes logic - please refer to the note aboveSwiftpack is being maintained by Petr Pavlik | @ptrpavlik | @swiftpackco | API | Analytics