Search Overlay

Going Live

This page describes how to set up currency accounts and move from the Test to the Production environment.

Multiple Accounts

You can use the default account to process Visa and Mastercard card payments (using the Card Payments, Customer Vault, Hosted Payments, and 3D Secure APIs). You need to open separate accounts for other card brands. You also need a separate account for each type of Direct Debit payment method, and for each of the alternate payments methods supported by Paysafe you want to use (for example, SOFORT and BOKU).

If you want to support payments in a different currency, you will need additional accounts for each payment method/currency combination. For example, to process card and SEPA direct debit payments in EUR and GBP you would need four accounts: SEPA Direct Debit EUR account, SEPA Direct Debit GBP account, Card Payments EUR account, and Card Payments GBP account. See the following image:

  • If you need accounts to support additional card brands such as Amex, Diners, and JCB, please Contact Support.
  • All your accounts can be set up to use the same API key (and in some cases, this will happen automatically). Please contact Customer Support for more information.

Using Currencies with Production Accounts

A production account has an associated currency in which funds are settled (paid into the account). For example, if you have a GBP account, funds will be paid into your account in GBP. The default account currency is used to take and process payments from your customers. For a list of currencies and the corresponding codes, see Currency Codes.

NOTE: You will incur currency conversion costs when the currency in which customer payment is made is different from the currency of the merchant account into which the funds are settled. You must therefore open a separate merchant account for each currency you want to accept funds in.

Managing Payments via the Merchant Back Office

You can sign in to the Paysafe Merchant Back Office to view the status of your transactions, configure customized reports, and perform additional payment actions such as bulk uploads and payments via the Virtual Terminal.

NOTE: We recommend that you set up customized reports to receive details of transactions, settlements, and chargebacks.

Currency Processing and Settlement Options

You can override the default processing currency by specifying in your API request the currency code of the currency to be used for processing the transaction (using the currencyCode parameter). For example:


"amount": 10098,
"currencyCode" : "CAD",

Example currency and account code

If you have multiple accounts with the same currency, you should use the following code to first specify the payment currency and then identify the account into which the transaction funds should be sent. This makes use of the extendedOptions parameter, where you can specify your merchant account. If the settlement account is not selected, the payment will be made into your default account.

NOTE: This feature is available only with the Hosted Payments API.

"merchantRefNum" : "ZUQTNPN0K1O442NZUA",
"currencyCode" : "EUR",
"totalAmount" : "2894",
"extendedOptions" : [{"key" : "merchantAccount", "value" : "100XXXXX"}]

Moving from Test to Production Environment

The Test and Production environments are two separate integrations. Your API requests in the Production environment must use your Production account details:

  • Production merchant account number
  • Production API Key

To process live transactions, your API requests should point to the Production API endpoints:

For example:

You will need to repeat any configuration changes made to your Test account on the Production account. Keep a record of any changes requested and carried out.

Go Live Checklist

See below for details of website compliance and other checks that should be completed before going live.

NOTE: Before switching an account to live, Paysafe will carry out compliance checks on all merchants who are using Paysafe as their acquirer. For merchants using a different acquirer, additional compliance checks may apply. Contact your acquirer for details.

Payment processing

  • Make sure you have submitted the necessary documentation or evidence to support any PCI DSS compliance requirements.
  • Ensure you have tested your supported payment methods in a number of scenarios, including success, failed, and pending, and in an end-to-end process (i.e., from website order through to final settlement and payment, including handling of cancelled transactions and refunds).
  • Ensure your customer support, operations, logistics, and finance teams have been trained to support the new system.
  • Please supply any additional information requested by your Paysafe Sales representative or account manager.

Website compliance

Before you go live with the Paysafe service, please make sure that your e-commerce website provides the following information:

  • Payment Method Logos of the payment methods you are offering through Paysafe. For a list of icons you can use, see Payment Method Logos.
  • Company Name and Registration Number (if applicable)
  • Full Terms and Conditions of Your Service
  • Privacy Policy – complying with local Data Protection legislation and explaining how you deal with customers’ personal information. Your policy should state that you do not share or sell customers’ personal information to third parties.
  • Returns Policy – describing what happens when a customer wants to return an item ordered on your website. Your policy should include a “cooling off” period for your online customers to decide if they want to cancel the order on your website and/or return the goods or services.
  • Your Contact Details
    • Where customers can reach you and return unwanted or faulty items. You should include the business address from which you operate or trade, an email address, and a phone number. Note that providing a PO box as a contact address is not acceptable.
    • When you submit your application please send us: i) Website addresses – URLs to the pages on your website that display the above information; and ii) any login details needed to access these URLs.

Further information may be required for higher-risk businesses. You will also be asked to confirm that your website is owned by your business or organization.

NOTE: Businesses trading in the European Union must provide this information to comply with the Distance Selling Regulations. Similar regulations apply to other regions.