- REST APIs
- Welcome
- Card Payments
- 3D Secure 2
- Vault
- Getting Started
- Using the API
- Typical API Calls
- Verify That the Service Is Accessible
- Create a Profile for a Customer
- Add an Address to a Profile
- Add a Card to a Profile
- Add a Bank Account to a Profile
- Create an Apple Pay Single-Use Token
- Create a Google Pay Single-Use Token
- Create a Mobile Single-Use Token
- Create a Direct Debit Single-Use Token
- Process a Transaction Using a Payment Token
- API Reference
- Test and Go Live
- Direct Debit
- Apple Pay
- Google Pay
- Business Portal
- Partner Portal
- Alternate Payments
- Reports API
- Platforms
- Overview
- Accounts API V1
- Getting Started
- Using the API
- Typical API Calls
- Verify That the Service Is Accessible
- Create a New Merchant
- Create a New Merchant Account
- Create a New User
- Add an Address
- Create a Business Owner
- Add a Business Owner Address
- Add a Business Owner Identity Document
- Add a Merchant Bank Account
- Accept Our Terms and Conditions
- Activate the New Merchant Account
- Validate the Bank Account
- Enable Webhooks to Receive Application Statuses
- Test and Go Live
- Subaccounts
- Applications API
- Split Payouts
- Balance Transfers
- Paysafe Payments API
- Paysafe Checkout
- Paysafe JS
- Payments API
- Bad Bin API
- Reference Information
- SDKs
- Mobile SDKs
- Additional Documentation
- Resources and Support
- Shopping Carts
- Classic APIs
- Glossary
Known Issues in Android 4.4
Please Note: As an ISV / Paysafe Partner, you will need to complete all of the below "merchant" steps on behalf of the Parent Merchant Legal Entity (PMLE) that your merchants will be operating under.
Paysafe Android SDK supports Android version 4.4 and above. However there are some known issues that occur only on Android 4.4 and are not handled by the SDK. You should consider resolving them in your application.
Update your security provider
Under the curtains Paysafe Android SDK uses secure connections to backend services. Android relies on a security provider to provide this secure communication. The default security provider in Android 4.4 has some vulnerabilities and you must update it.
It is mandatory to update the security provider before you create instance of PaysafeApiClient. Good place to do it is in your Application.onCreate() method.
For more information refer to the official documentation: Update your security provider to protect against SSL exploits
Notify the user to turn on Location Services
If the user has turned off his Location Services and your app declares one of the following permissions in AndroidManifest.xml:
You should make sure the user has turned on his Location Services before creating an instance of ThreeDSecureService
This step is necessary, because if the Location Services are not turned on before creating an instance of ThreeDSecureService the initialization would fail with NullPointerException. This is a known issue and we are working to fix it.