GlobalTransactionCharge

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Shop ID
• Public Key
• Secret Key
• Three DS Mode -> (Simple or Advanced — defaults to Advanced if not set)
• Provider URL -> (preset to GlobalTransactionCharge's gateway, not user-selectable)
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. You can set these parameters according to available currencies and features for your GlobalTransactionCharge account, but it is necessary to check details of the connection with your Corefy account manager.

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "55041b5b-adfd-4073-a92b-fd8b495a4cc1",
        "email": "johnsmith@gmail.com"
      },
      "reference_id": "86e68af6-6b95-4cc0-be16-e4df8044604c"
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "bc75bc54-5023-4f98-8c0d-ec5ed7e8f380",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-05-14",
        "address": {
          "country": "DE",
          "region": "Berlin",
          "city": "Berlin",
          "post_code": "10115",
          "full_address": "1st Street 1"
        }
      },
      "reference_id": "08f5e97c-1170-4bda-9625-3bde3c6dcd20"
    }
  }
}

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.

Currently available options (2)

• ignore_callback - suppresses processing of callbacks received from GlobalTransactionCharge
• send_customer_data - sends the customer's billing details (name, phone, address) to GlobalTransactionCharge

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

LANG is the exception to this rule — see below.

Currently available constants (constant -> Corefy API field)

• DESCRIPTION -> description
• REASON -> description (used for refunds specifically, instead of DESCRIPTION)
• EMAIL -> customer.email
• COUNTRY -> customer.address.country / customer.metadata.country
• CITY -> customer.address.city / customer.metadata.city
• STATE -> customer.address.region / customer.metadata.state
• ZIP -> customer.address.post_code / customer.metadata.zip
• ADDRESS -> customer.address.full_address / customer.metadata.address
• LANG -> always used as sent — there is no request-side field to override it, set this constant to control the language GlobalTransactionCharge uses