Skip to main content

Deposits

Introduction​

The deposit operation allows customers of Paysafe Embedded Wallet to load funds into their embedded wallet accounts.

tip

Embedded wallet deposits are being updated to a more simplified and consistent solution approach, that supports building direct end-user applications using Paysafe Embedded Wallet SDK for enhanced security and reduced TCO and TCD for partners.

The new deposit approach leverages Paysafe Embedded Wallet SDKs to offer enhanced security and reduced TCO and TCD for partners adopting the solution.

The supported deposit methods are:

  • Debit or Credit card
  • ACH Direct Debit for US customers (In Development)
  • Bankwire deposit using VIBAN or Virtual Account for EU and UK customers (In Development)
  • other deposit methods are coming...

For more information check:

Bankwire deposit​

Paysafe Embedded Wallet supports bank transfer deposits using customer assigned vIBANs in Paysafe partner bank. Once offline customer deposit reaches Paysafe partner bank, customer's wallet is funded with the corresponding amount.

Virtual IBAN is assigned to each customer during the onboarding process. You can obtain the vIBAN using Accounts API.

GET https://api.paysafe.com/digitalwallets/v2/accounts
Get account information
[{
      "id": "509876034",
      "customerId": "5435323362",
      "currencyCode": "GBP",
      "totalBalance": 55000,
      "availableBalance": 50000,
      "virtualInstrument": [
        {
          "instrumentType": "SEPA_BANK_ACCOUNT",
          "iban": "NL74ABNA1231242344",
          "bic": "ABNANL2APIP",
          "status": "ACTIVE"
        }
      ],
  "creationTime": "2019-08-24T14:15:22Z",
  "hasVirtualInstrument": true
}]

Bank Transfer Deposit Steps​

Bank transfer depositBank transfer depositBank transfer depositBank transfer deposit

  1. Merchant must show vIBAN or Paysafe details as account holder upon bank transfer payment option on Merchant website

  2. Customer initiates bank transfer from their bank to their vIBAN or Paysafe account

  3. Paysafe performs vIBAN and name match when deposit is received in Paysafe partner bank

  4. The transaction amount will be credited to the customer wallet

  5. Where applicable, the merchant deposit fee amount will be debited from the customer wallet

    info

    Customers can only be charged a pre-defined fixed fee for bank transfer deposits.

  6. Merchant recieves a TransactionUpdateWebhook when funds are deposited in the wallet

    POST https://<merchant callback URL>
    Transaction update webhook
    {
        "id": "3aeb9c63-6386-46a3-9f8e-f452e722228a",
        "timestamp": "2021-07-15T17:54:12Z",
        "transaction": {
            "id": "544232",
            "merchantRefNum": "abcd1234",
            "customerId": "1234",
            "accountId": "212345",
            "type": "DEPOSIT",
            "slipId": "121345",
            "amount": 1000,
            "currencyCode": "EUR",
            "creationTime": "2021-07-15T17:54:12Z",
            "direction": "CREDIT",
            "paymentType": "BANK_TRANSFER",
            "description": "Transaction description.",
            "status": "COMPLETED"
        }
    }

Virtual Bank Accounts​

Paysafe Embedded Wallet provides an option to create a virtual Bank Account and link it to a wallet. Once created any funds wired to that Bank Account can be credited automatically to the associated wallet.

Card Deposits​

Card deposits via VISA and MasterCard are supported for partners in accordance with the applicable PCI DSS compliance levels. 3D secure authentication provides an additional layer of protection.

Partners should leverage the provided web and mobile SDKs to implement the deposit flow and can choose between various development options, depending on their PCI DSS compliance level and customization needs.

The deposit API supports either re-using an existing card for deposit or entering new card information during the deposit process.

tip
  • Only cards that previously have been successfully deposited can be re-used for new deposits.
  • User consent is required for storing card information in Embedded Wallet.

PCI DSS Compliance​

The Payment Card Industry Data Security Standard (PCI DSS) is an information security framework designed to help merchants and service providers protect debit and credit card transactions from data breaches.

Your PCI level and integration method with Paysafe will determine the PCI DSS compliance requirements you must meet.

Payment card brands such as:

  • Visa
  • Mastercard
  • American Express
  • Discover
  • JCB

each maintain their own compliance programs and transaction thresholds across the four levels of PCI DSS compliance.

As a result, a merchant or partner may have different PCI compliance levels for each payment brand.

PCI DSS Compliance Levels​

Partners and merchants are classified into four PCI Compliance levels, based on the number of card transactions they process annually (12-month period).

The strictest level of PCI DSS Compliance is Level 1. Partners and merchants that are PCI DSS Level 1 compliant may access cardholder data directly.

Partners and merchants that are not PCI DSS Level 1 compliant cannot access cardholder data directly. In such cases, cardholder data must be collected using external solutions that meet PCI DSS Level 1 Compliance requirements.

tip

For detailed guidance on PCI DSS compliance levels, visit PCI DSS Compliance Levels. This resource provides:

  • Detailed descriptions of each PCI DSS compliance level
  • Key requirements associated with each level
  • Guidance on determining your own PCI DSS compliance level

Web Integration​

Partners that are PCI DSS Level 1 compliant may access cardholder data directly.

This allows them to:

  • Integrate with the Paysafe SDK user-facing APIs.
  • Build their own deposit interface from scratch.
tip

When requesting SDK JWT tokens, partners must include the pci-dss-1 scope.

If this scope is missing, the Paysafe Consumer API will treat the partner as non-PCI DSS Level 1 compliant and automatically redirect the flow.

Card Card Card Card

Partners that are not PCI DSS Level 1 compliant are prohibited from directly accessing cardholder data.

For web-based implementations, PCI DSS requirements are met by using the Paysafe hosted page, a PCI DSS Level 1–compliant external payment integration, to collect cardholder information.

tip

Existing card instruments stored with user consent can still be used.

warning

When redirecting to Paysafe hosted pages, developers should be aware of certain special cases. Paysafe supports embedding within iframes, but during the 3DS challenge, the flow may sometimes redirect outside the iframe.

To ensure a smooth integration and provide the best user experience, we recommend one of the following approaches:

  • Open the hosted page in a new browser window or tab, avoiding iframes altogether.
  • Embed the page inside an iframe and implement proper handling to manage cases where the flow exits the iframe during the 3DS challenge.
Card Card Card Card

Mobile Integration​

Partners that are not PCI DSS Level 1 compliant are prohibited from directly accessing cardholder data.

In mobile-based implementations, cardholder information must be collected through the Paysafe Mobile SDK, a PCI DSS Level 1–compliant third-party integration.

tip

When requesting SDK JWT tokens, partners must include the pci-dss-1 scope.

If scope is not present in the JWT access token the Paysafe Consumer API will treat the partner as non-PCI compliant and automatically redirect the flow.

Card Card Card Card