BoxPlat

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Login
• Password
• SSL Certificate (upload)
• SSL Password
• API URL (optional, leave blank for the default)

Choose Currency and Features. You can set these parameters according to available currencies and features for your BoxPlat account (EUR, USD confirmed), 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; 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_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "address": {
          "country": "DE",
          "city": "Berlin"
        }
      }
    }
  }
}

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",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "DE",
          "city": "Berlin",
          "post_code": "10115",
          "full_address": "1 Main street"
        }
      }
    }
  }
}

customer, customer.address, and customer.email are all required - BoxPlat rejects a request missing any of them before it's even sent. The cardholder's full name must also resolve to a Latin-alphabet first and last name - this comes from customer.name via the checkout/SDK layer, not from this request directly. This connector also supports USD (payment_card_usd_hpp).

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 (3)

• time_to_finalize - automatically fails a transaction if BoxPlat hasn't returned a final status within this many hours.
• save_cash_flow - stores BoxPlat's own cash-flow/settlement breakdown data alongside the transaction.
• ignore_card_network - changes how card-network-specific extra data is attached to the request.

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)

Currently available constants (constant -> Corefy API field)

• OS -> not a request-field fallback - always used as-is for the synthetic device/browser fingerprint sent with every 3DS request (default: Windows)
• OS_VERSION -> same as OS (default: x86_64)
• PLUGINS -> same as OS (default: a generic PDF-viewer plugin list)
• IS_MOBILE -> same as OS (default: false)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Login
• Password
• SSL Certificate (upload)
• SSL Password
• API URL (optional, leave blank for the default)
• Balance Currency (optional)

First request to Corefy API

What it does: creates a payment-invoice and returns a redirect link to BoxPlat's hosted payment page. This flow reads nothing beyond the generic envelope - no customer/fields data is forwarded to BoxPlat at all, so there's no MIN/MAX distinction to make.

Payment - Actual

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

This connector may support other currencies/local methods beyond EUR - confirm with your Corefy account manager which ones are enabled for your account.

Options

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (1)

• force3d - forces a 3D Secure challenge on every payment, regardless of what BoxPlat/the card issuer would otherwise require.

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.

Currently available constants (constant -> Corefy API field)

• LANGUAGE -> not a request-field fallback - there's no per-request override for this; set it to control the language shown on BoxPlat's hosted payment page for this service.

Connect Provider account in Corefy Dashboard

Uses the same Provider account connection as Payments above - one connection covers both directions, there's nothing extra to fill in for payouts specifically.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds 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,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith"
      },
      "fields": {
        "card_number": "4111111111111111",
        "card_exp_month": "12",
        "card_exp_year": "27"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "7976b4ce-fadd-4585-baa0-6b02c65351dc",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "DE",
          "region": "Berlin"
        },
        "metadata": {
          "ip": "203.0.113.10",
          "date_of_birth": "1990-05-12"
        }
      },
      "fields": {
        "card_number": "4111111111111111",
        "card_exp_month": "12",
        "card_exp_year": "27"
      }
    }
  }
}

fields.card_number and fields.card_exp_month/card_exp_year are required, as is customer.name - BoxPlat rejects a payout without a customer name, and that name must be exactly two Latin-alphabet words (first and last name only - no middle names, no non-Latin characters). This connector also supports payouts in RUB, USD, BRL, CAD, THB, VND, INR, MYR, AUD, PKR, NZD, TRY, AZN, KZT, NOK, ZAR, and PLN (use payment_card_<currency> as the service code).

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