Skip to content

Logo

Paysafe

It starts here

Website: paysafe.com

Set up Account H2H merchant account

Step 1: Create Merchant Account

To create an account send connection request at the paysafe.com or contact manager directly. Submit the required documents to verify your account and gain access.

Step 2: Get required credentials

Credentials that have to be issued:

  • API Username
  • API Password
  • Account ID
  • Secret key

Connect Merchant Account

Step 1. Connect H2H account at the Corefy Dashboard

Press Connect at Paysafe Provider Overview page in 'New connection' section and choose H2H Merchant account option to open Connection form.

Connect

Enter credentials:

  • API Username → api_user_name
  • API Password → api_password
  • Account ID → account_id
  • Secret key → secret_key
  • Save Instant Token → True/False
  • Test mode → True/False
  • Currency → choose currency (You can set these parameters according to available currencies and features for your Paysafe wallets and services, but it's necessary to check details of the connection with your Corefy account manager.)

Success

You have connected Paysafe H2H merchant account!

API examples:

Minimum data set to create a payment invoices for payment_card_gbp_hpp service

SALE

POST /api/commerce/payment-invoices HTTP/1.0
{
  "data":{
    "type":"payment-invoice",
    "attributes":{
      "service":"payment_card_gbp_hpp",
      "commerce_account":"Hello World",
      "currency":"GBP",
      "amount":1,
      "flow":"charge",
      "gateway_options":{
        "cardgate":{
          "tokenize":""
        }
      },
      "customer":{
        "reference_id":"77777",
        "name":"John Wick",
        "email":"johnwick@gmail.com",
        "address":{
          "country":"UA",
          "city":"Kyiv",
          "street":"test street",
          "post_code":"65000"
        }
      },
      "test_mode":true,
      "options":{
        "allow_partially":false,
        "bypass_hpp":false,
        "send_operation_context_on_return":false
      },
      "reference_id":"256f9a70-2653-4cba-ab9e-34d6c8e9d35e",
      "service_fields":[
      ]
    }
  }
}

Maximum data set to create a payment invoices for payment_card_gbp_hpp service

SALE

POST /api/commerce/payment-invoices HTTP/1.0
{
  "data":{
    "type":"payment-invoice",
    "attributes":{
      "service":"payment_card_gbp_hpp",
      "commerce_account":"Hello World",
      "currency":"GBP",
      "amount":1,
      "flow":"charge",
      "gateway_options":{
        "cardgate":{
          "tokenize":""
        }
      },
      "customer":{
        "reference_id":"66666",
        "name":"John Wick",
        "email":"johnwick@gmail.com",
        "phone":"+380647551234",
        "address":{
          "full_address":"test street 123",
          "country":"UA",
          "region":"Kyiv",
          "city":"Kyiv",
          "street":"test street",
          "post_code":"65000"
        }
      },
      "test_mode":true,
      "options":{
        "allow_partially":false,
        "bypass_hpp":false,
        "send_operation_context_on_return":false
      },
      "reference_id":"9e06046b-4f20-4078-b6a5-e98e8508702d",
      "service_fields":[
      ]
    }
  }
}

Constants

Сonstants

If some parameters are not sent in the transaction creation request, they will take the values from the set constants.

Here is a list of constants with their corresponding parameters:

  • FIRST_NAME → customer [first_name]
  • LAST_NAME → customer [last_name]
  • PHONE → customer [phone]
  • EMAIL → customer [email]
  • COUNTRY → customer [address] [country]
  • REGION → customer [address] [region]
  • CITY → customer [address] [city]
  • POST_CODE → customer[address][post_code]
  • STREET → customer [address] [street]
  • BROWSER_IP → merchant_account [browser_ip]
  • CARD_HOLDER → merchant_account [card_holder]
  • FUNDING_TRANSACTION_TYPE → merchant_account [funding_transaction_type]
  • Documentation link
    • appends on confirm payment and confirm recurrent payments endpoint /payments
    • The fundingTransaction object is used to identify authorization requests that are categorized as funding transactions by the merchant in order to provide additional information for the purpose of a transaction. It can be used by merchants registered with MCC 4722, 4829, 6012, 6051, 6211, 6540, 7800, 7801, 7802, 7994, 7995 or 9406. MCC 7995 is valid only for MC Funding as per the use cases presented in the table below. The relevant value will be assigned automatically by the Paysafe as per the merchant registration with card schemes and their applicable MCC.
    • FUNDING_TRANSACTION_TYPE
    • FUNDING_TRANSACTION_TYPE

Provider Options

Provider_Options

  • Finalizing on auth

    • completing of success sale depends on:
    • if merchant_account[provider_options][allow_finalyze_by_auth] = false => impossible
    • if merchant_account[provider_options][allow_finalyze_by_auth] = true

  • Finalizing on auth with token saving

  • Generate data for customer

    • No = The transaction is sent with data from the customer or constants.
    • Yes = Check for the presence of name, email, ip in the request. If any of these are missing, the transaction will be spoofed and not sent. If all phone, country, city, postal code, street, region are present, we send them to the provider. If not, we generate the data.

  • Generate region for customer

  • Send payment facilitator in request

  • Requestor challenge preference

Question

"Still looking for help connecting your Paysafe account?" Please contact our support team!