Transact Pro

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• GUID
• Secret Key
• Google Pay MID (optional)
• Apple Pay Merchant ID (optional)
• Apple Pay Display Name (optional)
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features; check with your Corefy account manager which are enabled for your 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. Apple Pay and Google Pay are handled through Corefy's SDK the same way as on other connectors - no extra fields in the API request itself, just make sure the matching credentials above are set.

Payment - MIN

POST /api/payment-invoices

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

This connector also supports USD.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "FR",
          "city": "Paris",
          "street": "1 Main street",
          "post_code": "75000"
        }
      }
    }
  }
}

customer is entirely optional - anything you don't send falls back to the Constants below.

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

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 (including the customer's browser info, normally collected automatically) are missing in the request. The same constants apply to card, Apple Pay, and Google Pay payments.

Priority (predictable rule): 1. If a value is present in the request/collected automatically -> Corefy uses that 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)

Currently available constants (constant -> Corefy API field)

• customer_email -> customer.email
• customer_phone -> customer.phone
• customer_country -> customer.address.country
• customer_city -> customer.address.city
• customer_street -> customer.address.street
• customer_zip -> customer.address.post_code
• browser_accept_header, browser_language, browser_color_depth, browser_screen_height, browser_screen_width, browser_tz, browser_user_agent, browser_java_enabled -> the customer's browser/device fingerprint, normally collected automatically by Corefy's checkout

Refunds

Transact Pro supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open Transact Pro in the provider directory and press Connect at Transact Pro Provider Overview page in the New connection section. Choose Provider account.

Step 2 - Fill in fields and select settings

• GUID
• Secret Key
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds directly to a card.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "FR",
          "region": "IDF",
          "city": "Paris",
          "street": "1 Main street",
          "post_code": "75000"
        },
        "metadata": {
          "ip": "203.0.113.5"
        }
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

customer is entirely optional - everything is only forwarded to Transact Pro as recipient/billing details.

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

Constants (fallback fields)

Same idea as the Payments flow above - these are only used when the matching request field is missing.

Currently available constants (constant -> Corefy API field)

• customer_email -> customer.email
• customer_phone -> customer.phone
• customer_country -> customer.address.country
• customer_state -> customer.address.region
• customer_city -> customer.address.city
• customer_street -> customer.address.street
• customer_post_code -> customer.address.post_code
• user_ip -> customer.metadata.ip