Skip to main content
Paysafe is a global payments provider offering card acquiring alongside its own family of digital wallets and prepaid products. Through Primer you can process cards, digital wallets and Paysafe’s alternative payment methods on a single connection.

At a glance

Supported payment methods

Supported capabilities

CapabilityCardApple Pay and Google PayAlternative payment methods
Authorization and captureYesYesYes
Partial captureYesYesNo
Authorization adjustmentNoNoNo
RefundYesYesYes
Partial refundYesYesYes
Multiple refundsYesYesYes
Recurring and merchant-initiated paymentsYesYesNo
Network tokensYesYesNot applicable
Some capabilities must be enabled on your Paysafe account. Contact Paysafe to confirm which features are available to you.

3D Secure

Primer performs 3D Secure authentication using the Perform 3DS action and passes the authentication result to Paysafe. You do not need to run 3D Secure on the Paysafe side.

Get started with Paysafe

Before you begin

If this is your first connection, make sure to follow the Get started guide to begin processing payments with Primer. Complete your account setup with the Paysafe Onboarding Team before you connect. Paysafe provisions merchant IDs per payment method, so your account must be fully onboarded for every method you intend to offer.

Credentials

Paysafe issues two credential pairs, one public and one server side. Both are required.
FieldWhere to find it
Public usernamePaysafe Optic Portal, under Developer > API Keys. Use the username shown for the Public user.
Public passwordPaysafe Optic Portal, under Developer > API Keys. Use the key shown for the Public user.
Server usernamePaysafe Optic Portal, under Developer > API Keys. Authenticate with your Optic Portal password to reveal the Secret Key, then use the username shown for the Server user.
Server passwordPaysafe Optic Portal, under Developer > API Keys. Authenticate with your Optic Portal password to reveal the Secret Key, then use the private key shown for the Server user.

Configure in the Dashboard

1

Add Paysafe to your Dashboard

Go to Integrations, select New integration, search for Paysafe and enter your credentials.
2

Configure webhooks in Paysafe

Log in to the Paysafe Optic Portal and go to Developer > Webhook configurations, then select Add new configuration and:
  • Select the payment method you want the configuration to cover, either by merchant ID or by payment method name.
  • Paste your Primer callback URL into the webhook URL field.
  • Select the environment, where you can also test connectivity.
  • Tick the events you want enabled.
Select Create webhook. A confirmation message appears if it was created successfully.Paysafe scopes webhook configurations per payment method, so repeat this step for every payment method you offer.
3

Activate the payment methods on the Checkout

Go to Checkout and activate the Paysafe payment methods you want to offer.
4

Route payments with Workflows

In Workflows, select Paysafe in the Authorize payment action.

Saved cards and merchant-initiated payments

Paysafe supports recurring and merchant-initiated payments on cards, Apple Pay and Google Pay. See recurring payments for the general Primer flow.

Considerations

  • Account onboarding gates everything. Paysafe provisions merchant IDs per payment method through its Onboarding Team. A method you have not been onboarded for will fail even if it is active on your Checkout.
  • Webhooks are configured per payment method. Unlike processors with a single account-level endpoint, Paysafe requires a webhook configuration for each payment method. A missing configuration shows up as payments that never reach a final status.
  • Two credential pairs are required. The public pair and the server pair serve different calls. Entering one pair in both sets of fields produces authentication errors.
  • Network tokens are supported. Primer can send network tokens to Paysafe, which can improve authorization rates on repeat payments.

Test in sandbox

Connect your Paysafe test account to your Primer Sandbox environment.

Troubleshooting

Primer maps Paysafe’s response codes to its own decline reasons. See decline codes for the full list.

Go live

Before switching to production, confirm that:
  1. Your Paysafe production account is fully onboarded for the payment methods you want to offer.
  2. You have added Paysafe in your Primer production environment using your production credentials, including both the public and server pairs.
  3. You have created a production webhook configuration in the Paysafe Optic Portal for every payment method you offer.
  4. You handle the PAYMENT.STATUS webhook and fulfil orders only on a final status.