Sense Bank

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Account ID
• Username / Password
• Username for onboarding / Password for onboarding
• Username for cryptogram / Password for cryptogram
• Merchant ID, Company city, Company legal name, Company trade name, Contact email, EDRPOU, Website URL -> optional, used for the one-time company onboarding call
• Currency / Features -> choose values available for your account (UAH)
• 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. Card, Apple Pay, and Google Pay are all supported on this same connection.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "09fe59f3-83b4-43f7-bb42-f77b9ca281a8",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10,
      "customer": {
        "reference_id": "60e17597-c8e5-4794-98ea-ee218665b1ef"
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "test@test.com"
      }
    }
  }
}

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

• use_tokenize -> optional, boolean - required to be enabled for any token-based (saved card) payment; if a payment is routed through the tokenize flow while this is off, the payment fails immediately.
• send_refid -> optional, boolean - conveys your own reference/description data to Sense Bank.
• quick_reconcile_on_sale -> optional, boolean - on a non-final sale response (3DS or non-3DS), sets the reconcile-required resolution so Corefy starts fast reconciliation instead of waiting for the regular schedule.
• payment_purpose_key -> optional, string - the metadata key Corefy reads the payment purpose/description from.
• send_cof_trans -> optional, boolean - sends a COF_TRANS (card-on-file transaction) flag, sourced from customer.metadata.COF or the cof_trans Constant.
• invalidate_legacy_tokens -> optional, boolean - clears out a previously stored token if it predates the current token-versioning scheme, forcing a fresh tokenization instead of reusing it.
• waiting_token_time_in_minutes -> optional, number - how long to wait for an asynchronous tokenization webhook before falling back to an active status check.

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)

These feed the 3DS browser-fingerprint data (clientInfo) sent on payment completion, falling back to the request's own real browser info when available:

• OS -> browser OS name, defaults to Windows if neither sent nor set
• OS_VERSION -> browser OS version, defaults to 10
• IS_MOBILE -> whether the browser is mobile, defaults to false
• PLUGINS -> browser plugin list, defaults to Chrome PDF Plugin, Chrome PDF Viewer, Native Client
• COF_TRANS -> only used when send_cof_trans is enabled

Refunds

Sense Bank supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment). The original payment's ID is always required to process a refund.