Kale.Money

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

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

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johndoe@email.com"
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "johndoe@email.com",
        "phone": "+448650405942",
        "address": {
          "full_address": "Shevchenka str",
          "country": "US",
          "region": "NY",
          "city": "New York",
          "post_code": "777777"
        }
      }
    }
  }
}

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)

• ignore_callback - skips Kale.Money's callback for finalizing the transaction and relies on reconciliation instead.

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)

• EMAIL -> customer.email
• PHONE -> customer.phone
• FIRST_NAME -> customer.name (first part)
• LAST_NAME -> customer.name (last part)
• ADDRESS -> customer.address.full_address
• CITY -> customer.address.city
• POST_CODE -> customer.address.post_code

This account type covers Apple Pay and Google Pay - Kale.Money handles both wallets through the same redirect flow.

Connect Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Public key
• Private key
• Test Mode -> (enable if you are using sandbox credentials)
• API URL (optional, overrides the default gateway endpoint - leave blank unless told otherwise)
• Currency / Features -> choose Apple Pay and/or Google Pay as available for your account

First request to Corefy API (MIN)

What it does: creates a payment-invoice and returns a redirect link to Kale.Money's hosted checkout page.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "applepay_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johndoe@email.com"
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "applepay_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Wick",
        "email": "johndoe@email.com"
      }
    }
  }
}

Use googlepay_eur_hpp instead of applepay_eur_hpp for Google Pay - the request shape is identical, only the service code changes. Unlike the H2H Merchant account flow, this account type has no address/phone fields at all - only customer.name (split into first/last) and customer.email are used, and there's no card data since the customer completes the wallet payment on Kale.Money's own hosted page.

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)

• WEBSITE_URL -> merchant website URL sent to Kale.Money (no per-request override - taken from your merchant profile by default)
• CUSTOMER_FIRST_NAME -> customer.name (first part)
• CUSTOMER_LAST_NAME -> customer.name (last part)
• CUSTOMER_EMAIL -> customer.email

These constants are configured per service (applepay_eur_hpp and googlepay_eur_hpp separately).