WhiteBIT

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Account ID
• API key
• Private key (optional)
• API URL
• Send metadata -> (optional): enable to forward your own metadata to WhiteBIT
• Currency / Features -> choose values available for your account (UAH, RUB, EUR, USD)
• Test Mode -> (enable if you are using sandbox credentials)

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. WhiteBIT may return a 3D Secure challenge redirect, or an OTP confirmation step, depending on the card.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6f7a8b9c-0d1e-4f2a-8b13-6c7d8e9f0a1b",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "7a8b9c0d-1e2f-4a3b-8c24-7d8e9f0a1b2c",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "customer@example.com",
        "phone": "+380991234567",
        "address": {
          "country": "UA",
          "city": "Kyiv",
          "post_code": "01001",
          "street": "Main street 1"
        }
      },
      "metadata": {
        "order_id": "order_123"
      }
    }
  }
}

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

• ignore_callback -> optional, boolean - relies only on an active status request to finalize the payment, instead of also accepting WhiteBIT's asynchronous callback.
• save_provider_instant_token -> optional, boolean - saves a token after a successful payment so it can be charged again later (recurring).
• generate_random_customer_data -> optional, boolean - generates random customer data on Corefy's side when your request doesn't include it, for providers that require some customer fields to be present.
• transliterate_customer_data -> optional, boolean - transliterates customer data to Latin characters before sending it to WhiteBIT.
• transliterate_card_holder -> optional, boolean - transliterates the cardholder name to Latin characters before sending it to WhiteBIT.
• set_description -> optional, boolean - sends your payment's description to WhiteBIT.
• duplicate_original_resolution -> optional, boolean - reuses the original payment's decline reason for a related operation instead of requesting a new one.

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)

• address -> customer.address.street
• city -> customer.address.city
• country -> customer.address.country
• post_code -> customer.address.post_code
• phone -> customer.phone
• email -> customer.email
• metadata_key / metadata_value -> fallback for metadata when Send metadata is enabled but the request doesn't include it
• browser_tz, browser_screen_width, browser_screen_height, browser_color_depth, browser_language, browser_java_enabled, browser_accept_header, browser_user_agent, browser_ip -> browser fingerprint fields used for 3D Secure, normally collected automatically by Corefy's checkout/SDK layer

Refunds

WhiteBIT does not support refunds through Corefy on the H2H Merchant account.

Recurring

WhiteBIT supports saving a card token on a successful payment (enable save_provider_instant_token) and charging it again later through Corefy's standard recurring flow.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Account ID
• API key
• Private key (optional)
• API URL (optional)
• Send metadata -> (optional)
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice (hosted/redirect payment) or a payout-invoice (card payout). Available currencies and services are read live from your WhiteBIT account - whatever WhiteBIT exposes for your account becomes available in Corefy for the matching currency.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8b9c0d1e-2f3a-4b4c-8d35-8e9f0a1b2c3d",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10
    }
  }
}

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "9c0d1e2f-3a4b-4c5d-8e46-9f0a1b2c3d4e",
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 10,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

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

• allow_conversion -> optional, boolean - allows a payment or payout to go through on a WhiteBIT service whose settlement currency differs from the one you requested.
• send_description -> optional, boolean - Payouts only; sends your payout's description to WhiteBIT.

Refunds

WhiteBIT does not support refunds through Corefy on the Provider account.