- 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
- Alternate Payments
- Reports API
- ISV Reports
- 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
Generating a Device Fingerprint
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.
The first step of processing a 3DS card payment is generating a device fingerprint.
- Start by passing the card BIN to the start() method of the ThreeDSecureService.
The start() method will further call ThreeDSStartCallback when a device fingerprint is generated.
error marker {{Androiddevicefingerprint}} on page 2533 - Pass your device fingerprint to your server.
The server must call the /authentications endpoint of the Paysafe REST APIs. The response from the /authentications call contains the 3DS challenge payload, which is handled by your application.
If the SDK fails to generate a device fingerprint, you will receive a ThreeDSecureError that contains useful information about the cause of the failure. When troubleshooting, you can start by checking the error code and detailed message. Below, you can check the currently supported error codes:
| Error Code | Value | Explanation |
|---|---|---|
| ERROR_CODE_CONNECTION_FAILED | 9001 | The operation failed due to a timeout or a connectivity issue. |
| ERROR_CODE_INVALID_API_KEY | 9013 | Invalid API key or API secret provided when creating a Paysafe API Client. |
| ERROR_CODE_INTERNAL_SDK_ERROR | 9014 | A general SDK error. The detailed message should provide additional information. |
| ERROR_CODE_INVALID_MERCHANT_CONFIGURATION | 9501 | The configuration of the provided merchant account is invalid. The Paysafe Support team should be notified. |
If you cannot solve the issue on your own, you can get in touch with the Paysafe Support at integrations@paysafe.com and provide them with the error correlation ID.