EasyBits.io

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open EasyBits.io in the provider directory and press Connect at EasyBits.io Provider Overview page in the New connection section.

Step 2 - Fill in fields and select settings

• Client code name
• Private key
• Public key (optional)
• Fee calculation type
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice. Card payments (payment_card_uah_hpp) redirect to a hosted page; card transfer and all crypto services (card_transfer_uah_invoice, bitcoin_btc_hpp, ethereum_eth_hpp, tether_erc20_usdt_hpp) show a QR code/invoice for the customer to pay with. customer is not used at all for Payments - no customer data is sent to EasyBits.io.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "7a8b9c0d-1e2f-4304-8a15-7c8d9e0f1a2b",
      "service": "bitcoin_btc_hpp",
      "currency": "BTC",
      "amount": 0.001
    }
  }
}

Payment - MAX

There is no MAX variant - the request above already includes every field EasyBits.io's Payments API accepts. No Options or Constants are configured for Payments.

Refunds

EasyBits.io does not support initiating refunds through Corefy. If EasyBits.io refunds a payment on its own side, Corefy reflects that status during reconciliation, but cannot trigger it.

Connect Provider account in Corefy Dashboard

Uses the same Provider account connected above - no separate connection step.

First request to Corefy API (MIN)

What it does: creates a payout-invoice. Supported methods: card (UAH, EUR), bank transfer (UAH, EUR), and crypto (BTC, ETH, USDT ERC20) - each needs different fields.

Payout - MIN (card)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "8b9c0d1e-2f30-4415-8b26-8d9e0f1a2b3c",
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 100,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Payout - MAX (crypto)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "9c0d1e2f-3041-4526-8c37-9e0f1a2b3c4d",
      "service": "bitcoin_btc",
      "currency": "BTC",
      "amount": 0.001,
      "fields": {
        "wallet_id": "bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh"
      }
    }
  }
}

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

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. They apply only to EUR card payouts.

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)

• FIRST_NAME -> customer.first_name
• LAST_NAME -> customer.last_name
• DATE_OF_BIRTH -> customer.date_of_birth
• COUNTRY -> customer.address.country

Refunds

Payouts do not support refunds.