The Billing

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Endpoint ID
• API Secret
• API URL (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. CVV is always required - non-CVV sales aren't supported. There's no merchant-side control over 3D Secure - it's handled transparently based on the card/issuer.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6e2a4c81-9b3d-4f5e-8a6c-7d8e9f0a1b2c",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

This connector also supports EUR, RUB.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "a1b2c3d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567"
      }
    }
  }
}

customer is entirely optional. For the cardholder's first/last name, this connector always uses the name embossed on the card - customer.name isn't used for this field.

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

No Options or Constants are configured for this connector.

Refunds

This connector does not support refunds.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Endpoint ID
• API Secret
• API URL
• External Account ID (optional)
• 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 via card, UK Faster Payments, or SEPA transfer, depending on your account. Required fields vary by method - the Dashboard shows the exact field list once a method is selected.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "f3e4d5c6-7b8a-4c9d-8e0f-1a2b3c4d5e6f",
      "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": "0d1e2f3a-4b5c-4d6e-8f7a-8b9c0d1e2f3a",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

customer.reference_id is forwarded as the recipient identifier for non-card payout methods (Faster Payments, SEPA transfer).

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

• generate_random_cardholder_data -> optional, boolean - if a payout is missing required recipient details (name, address) for the selected method, fills them in automatically instead of rejecting the payout - using the Constants below if set, or generated placeholder data otherwise. This option has no effect unless the recipient details are actually missing, and the Constants below have no effect unless this option is enabled.

Constants (fallback fields, only with Generate Random Cardholder Data)

• first_name / last_name -> recipient's name.
• country -> recipient's country (3-letter code).
• city -> recipient's city.
• full_address -> recipient's address.
• post_code -> recipient's postal code.