CCBill

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Username
• Password
• Merchant Account Number
• Merchant Subaccount Number
• Merchant Subaccount Number (charge token) (optional)
• Merchant Application ID (Frontend)
• Merchant Secret Key (Frontend)
• Merchant Application ID (Backend)
• Merchant Secret Key (Backend)

Choose Currency and Features. You can set these parameters according to available currencies and features for your CCBill 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; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request. CCBill runs a two-step 3D Secure flow - the initial sale can come back pending a completion step, which Corefy handles automatically.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8afec793-9b41-4dc4-b281-c76cc54ffb89",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "06fa1ea9-8a5b-4dbc-b67b-6236b3b9af3d",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10.04,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "US",
          "city": "Tempe",
          "region": "AZ",
          "full_address": "1 Main street",
          "post_code": "85281"
        }
      }
    }
  }
}

customer is entirely optional - anything you don't send falls back to the Constants below, or is simply left blank on CCBill's side.

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)

• ip_option - controls how the customer's IP address is prepared before it's sent to CCBill.
• use_sca_required_function - controls whether Corefy first checks with CCBill if 3D Secure/SCA is actually required before running the 3DS challenge.

Constants (fallback fields)

Constants are static values that Corefy can send to CCBill 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)

• EMAIL -> customer.email
• COUNTRY -> customer.address.country
• CITY -> customer.address.city
• STATE -> customer.address.region
• FULL_ADDRESS -> customer.address.full_address
• POST_CODE -> customer.address.post_code (used when starting the 3D Secure authentication step)
• ZIP_CODE -> customer.address.post_code (used when finalizing the sale, after 3DS)
• PHONE -> customer.phone
• FIRST_NAME / LAST_NAME -> parsed from customer.name (split on the first space) - used only when finalizing the sale, if neither the card data nor customer.name supplies a cardholder name

Refunds

This connector supports refunds: partial refunds are allowed, but only one refund per payment (multiple/split refunds are not supported). The original transaction ID is required to process a refund.