Skip to content

Logo

Bizon

Elevating Payment Processing

Supports in this guide: Payments

Provider website: bizon.one

What you need to do for start processing transactions (brief summary)

  1. Get your credentials (from Bizon)
  2. Connect in Dashboard
  3. Send an API request

Choose account type

Bizon has a single account type:

  • H2H Merchant account -> used for card payments (card data sent directly)

Bizon does not currently support payouts through Corefy. If you're not sure whether this fits your use case, confirm with your Corefy account manager.

Prerequisites: get from Bizon

Contact your Bizon account manager to get your account verified and receive the following credentials.

  • Login -> Corefy field login.
  • Password -> Corefy field password.
  • SSL Certificate (file) + SSL Password -> Corefy fields ssl_certificate/ssl_password -> Bizon authenticates every API call over mutual TLS; generate the client certificate as instructed by Bizon and upload it here.
  • API URL (optional) -> Corefy field api_url -> leave as default unless your account manager tells you otherwise.
Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Login
  • Password
  • SSL Certificate
  • SSL Password
  • API URL (optional)
  • Save OCT Token -> enable if you plan to use stored-credential recurring charges after an initial payment
  • Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features; check with your Corefy account manager which are enabled for your account.

Success

You have connected Bizon H2H Merchant 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. Bizon may return a 3D Secure (v1 or v2) challenge redirect depending on the card.

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
    }
  }
}

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": "FR",
          "region": "Ile-de-France",
          "city": "Paris",
          "full_address": "1 Main street",
          "post_code": "75000"
        }
      }
    }
  }
}

customer is entirely optional, but unlike most H2H connectors Bizon receives the full block when you do send it - name, phone, full address, city, region, post code, country, and email are all forwarded (transliterated to Latin characters automatically if sent in Cyrillic or another non-Latin script).

Note

For Canadian addresses (country: "CA"), send address.region as a recognizable province name or code - Bizon normalizes it to the correct 2-letter code automatically.

Important

CVV is always required - this connector does not support non-CVV transactions.

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

  • disable_secure3d20_return_url -> optional, boolean - omits the 3D Secure v2 return URL from the request; ask your account manager before enabling.

No Constants are configured for this connector.

Refunds

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

Additional info

  1. Authorize-then-capture is also supported, alongside immediate sale - if you need to authorize now and capture (or void) later, confirm the setup with your Corefy account manager.

  2. Stored-credential recurring charges are supported - with Save OCT Token enabled, a successful sale creates a reusable token Corefy can charge again later without the customer present; ask your account manager for details.

  3. Callback routing is automatic - Corefy generates the callback/return URL per transaction, nothing to configure in Bizon's own back-office.

FAQ / Troubleshooting

  • Invalid credentials / connection error -> double-check Login/Password and that the SSL Certificate/Password are valid and not expired - Bizon rejects the connection at the TLS layer if the certificate doesn't match
  • Sale rejected for missing CVV -> this connector always requires a CVV, non-CVV sales aren't supported
  • Currency or service is not supported -> confirm allowed currencies/features in your Bizon account and in Corefy

Question

Still looking for help connecting your Bizon account? Please contact our support team!