Katarun

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• API Key
• API Type -> Server-to-Server or Direct Post
• S2S Token (required only for Server-to-Server)
• Brand ID
• Webhook Public Key (optional)
• API URL (optional)

Choose Currency and Features. USD, EUR, and AZN are confirmed; check with your Corefy account manager which are enabled for your 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.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "US",
          "city": "New York",
          "full_address": "1 Main street",
          "post_code": "10001"
        }
      }
    }
  }
}

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

No Options are configured for this flow either.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Brand ID
• API Key
• Webhook Public Key (optional)
• S2S Token (optional)
• Currency -> single-select, choose from the currencies enabled for your account

First request to Corefy API (MIN)

What it does: creates a payment-invoice. Most local methods redirect to Katarun's hosted page; a few (MB WAY, Multibanco, Payshop) are also available as a "requisites" variant that returns payment details directly instead of a redirect - see Additional info.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "sepa_transfer_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": "sepa_transfer_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

customer requirements differ a lot by local method - some need nothing at all, others need a full address - see Additional info for the breakdown per method.

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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (1)

• finalize_by_protocol - switches which internal status map Corefy uses to finalize transactions.

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. These only apply to the five specific Payment services listed below - every other local method on this flow has no Constants fallback at all.

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), by service

• sepa_transfer_eur_hpp: EMAIL -> customer.email
• bank_transfer_jpy_hpp: EMAIL -> customer.email
• mybank2_eur_hpp, epay_eur_hpp, rapidtransfer_eur_hpp: EMAIL -> customer.email, COUNTRY -> customer.address.country

Connect Provider account in Corefy Dashboard

Uses the same Provider account connection as Payments above - one connection covers both directions, there's nothing extra to fill in for payouts specifically.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds to a bank account or a card.

Payout - MIN (bank transfer)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "bank_transfer_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123"
      },
      "fields": {
        "account_number": "DE89370400440532013000",
        "beneficiary_full_name": "John Smith"
      }
    }
  }
}

Payout - MAX (bank transfer)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "7976b4ce-fadd-4585-baa0-6b02c65351dc",
      "service": "bank_transfer_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567"
      },
      "fields": {
        "account_number": "DE89370400440532013000",
        "beneficiary_full_name": "John Smith"
      }
    }
  }
}

fields.account_number (IBAN) and fields.beneficiary_full_name are required. This connector also supports card payouts in EUR/USD (use payment_card_eur/payment_card_usd as the service, with fields.card_number required and fields.card_holder optional - falls back to customer.name).

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.

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), by service

• bank_transfer_eur: EMAIL -> customer.email, PHONE -> customer.phone
• payment_card_eur, payment_card_usd: EMAIL -> customer.email, PHONE -> customer.phone, COUNTRY -> customer.address.country, CITY -> customer.address.city, FULL_ADDRESS -> customer.address.full_address, POST_CODE -> customer.address.post_code