Kitopay

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Public key
• Secret key
• Currency / Features -> choose values available for your account (EUR, USD)
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice in two steps behind the scenes - Kitopay first registers the payment and returns a card-submission URL, then Corefy's checkout/SDK layer submits the card data to that URL directly (a PCI-compliant proxy), not as part of this request.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "4c7c201c-e332-468b-8615-1e6fe86b331b"
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "c22e66d5-48fa-41b0-b322-55a985204e50",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "4c7c201c-e332-468b-8615-1e6fe86b331b",
        "name": "John Doe",
        "email": "test@example.com",
        "phone": "+380680786663",
        "date_of_birth": "1990-01-01",
        "address": {
          "full_address": "Main street 1",
          "country": "UA",
          "city": "Kyiv",
          "region": "Kyiv",
          "post_code": "01001"
        }
      }
    }
  }
}

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 - for cascading to work correctly, ignores Kitopay's asynchronous callback and relies only on an active status request to finalize the payment.

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 -> an empty value is sent to Kitopay for that field

Currently available constants (constant -> Corefy API field)

• FIRST_NAME -> customer.name (first name)
• LAST_NAME -> customer.name (last name)
• EMAIL -> customer.email
• DATE_OF_BIRTH -> customer.date_of_birth
• COUNTRY -> customer.address.country
• CITY -> customer.address.city
• REGION -> customer.address.region
• FULL_ADDRESS -> customer.address.full_address
• POST_CODE -> customer.address.post_code
• COUNTRY_PHONE_CODE -> used to resolve customer.phone's country code when neither customer.address.country nor customer.phone are set
• PHONE -> customer.phone

Refunds

Kitopay does not support refunds.