Paysafe

It starts here

Supports in this guide: Payments, Payouts

Provider website: paysafe.com

What you need to do for start processing transactions (brief summary)

Choose account type
Get your credentials (from Paysafe)
Connect in Dashboard
Send an API request

Choose account type

Paysafe can be connected in different ways (depending on your needs):

If you do H2H card payments, Apple Pay, or Google Pay (card data sent directly) -> choose H2H Merchant account
If you do Skrill, Neteller, or paysafecard redirect payments, or payouts -> choose Provider account

If you're not sure which one to use, confirm with your Corefy account manager.

Prerequisites: get from Paysafe

Submit a connection request at paysafe.com/contact or contact your Paysafe account manager directly to get your account verified and receive the following credentials.

For H2H Merchant account:

API Username -> Corefy field api_user_name.
API Password -> Corefy field api_password.
Account ID -> Corefy field account_id.
Secret Key -> Corefy field secret_key.
Data Generator Secret Key (optional) -> Corefy field data_generator_secret_key -> only needed if you plan to enable the generate_data_for_customer Option below.
Google Pay Gateway MID (optional, Google Pay only) -> Corefy field google_pay_gateway_mid.

For Provider account:

API Username -> Corefy field api_user_name.
API Password -> Corefy field api_password.
Account ID -> Corefy field account_id.
Currency -> Corefy field currency -> single-select.

Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open Paysafe in the provider directory and press Connect at Paysafe Provider Overview page in the New connection section. Choose H2H Merchant account.

Step 2 - Fill in fields and select settings

API Username
API Password
Account ID
Secret Key
Save Instant Token
Data Generator Secret Key (optional)
Google Pay Gateway MID (optional)
Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. CHF, USD, EUR, GBP, DKK, AUD, and CAD are confirmed; check with your Corefy account manager which are enabled for your account. If you connect Apple Pay or Google Pay, select the matching feature too.

Success

You have connected Paysafe H2H Merchant account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_gbp_hpp",
      "currency": "GBP",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_gbp_hpp",
      "currency": "GBP",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "full_address": "1 Main street",
          "country": "GB",
          "region": "London",
          "city": "London",
          "street": "1 Main street",
          "post_code": "SW1A 1AA"
        }
      }
    }
  }
}

customer is optional - anything you omit falls back to the Constants below. This connector also supports Apple Pay and Google Pay on this same account (no separate service code needed).

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Options

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses. Card, Apple Pay, and Google Pay each have their own copy of these Options.

Currently available options (6 on card; 5 on Apple Pay/Google Pay)

allow_finalize_on_auth - treats a completed 3D Secure authentication as a final success, without waiting for settlement.
allow_auth_finalize_with_token_save (card only) - lets allow_finalize_on_auth still apply even when Save Instant Token is enabled.
generate_data_for_customer - requires customer.name/customer.email, and replaces unconvincing customer address data with provider-validated data.
generate_region_for_customer - requires a resolvable city/country (and region, where mandatory) before the sale is sent.
send_payment_facilitator - adds payment-facilitator/sub-merchant reporting data to the request.
requestor_challenge_preference - sets your 3D Secure challenge preference.

allow_finalize_on_auth

What it does: by default, Corefy waits for the actual charge/settlement confirmation before marking a 3D-Secure-authenticated sale as successful. Enabling this marks it successful as soon as the 3DS authentication itself completes.

When to use: enable it if you want the perceived completion to happen right after authentication rather than after settlement.

Default: false