Skip to content

Logo

Kluwp

Bespoke Payment Solutions

Supports in this guide: Payments

Provider website: kluwp.com

What you need to do for start processing transactions (brief summary)

  1. Get your credentials (from Kluwp)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from Kluwp

Contact your Kluwp account manager to get your account verified and receive the following credentials.

  • API Key -> Corefy field api_key.
  • Secret Key -> Corefy field secret_key -> used to sign every request.
Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • API Key
  • Secret Key
  • Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features; check with your Corefy account manager which are enabled for your account.

Success

You have connected Kluwp H2H Merchant 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. Kluwp may return a 3D Secure challenge redirect depending on the card. CVV is always required - non-CVV sales aren't supported.

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,
      "customer": {
        "reference_id": "cus_123",
        "address": {
          "country": "US"
        }
      }
    }
  }
}

This connector also supports EUR, AUD, BGN, BRL, CAD, CHF, CZK, DKK, HRK, HUF, NOK, NZD, PLN, SEK.

Important

customer and customer.address must be present in the request (even with empty fields inside) - the sale is rejected outright ("Customer data is required") if either is missing entirely. Browser/device data is also required for every sale ("Browser info is required") - this is normally collected automatically by Corefy's checkout/SDK layer, so it only becomes relevant for fully custom/headless integrations.

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",
        "date_of_birth": "1990-01-01",
        "address": {
          "country": "US",
          "city": "New York",
          "full_address": "1 Main street",
          "post_code": "10001"
        }
      }
    }
  }
}

Everything inside customer other than the address object itself is optional - name/full_address/city are automatically transliterated to Latin before being sent to Kluwp.

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 Constants are configured for this connector.

Options

  • ignore_callback -> optional, boolean - for cascading to work correctly, excludes finalizing the payment from the asynchronous callback; Corefy then relies only on an active status request (reconciliation) to finalize it.

Refunds

This connector supports full refunds only (no partial refunds), and only one refund per payment.

Additional info

  1. Callback routing is automatic - Corefy generates the callback/return URLs per transaction, nothing to configure in Kluwp's own back-office.
  2. Cards must support 3D Secure - if Corefy can't determine 3DS enrolment for a card upfront, the sale is rejected rather than attempted without 3DS.
  3. No payouts - this connector does not support payouts through Corefy.

FAQ / Troubleshooting

  • Sale rejected with "Customer data is required" or "Browser info is required" -> send a customer object with at least an (even empty) address, and make sure browser/device data reaches Corefy - this is normally automatic via the checkout/SDK layer
  • Invalid credentials / auth error -> verify API Key/Secret Key for the selected environment
  • Refund fails on a second attempt -> this connector only allows one refund per payment, and it must be a full refund
  • Currency or service is not supported -> confirm allowed currencies/features in your Kluwp account and in Corefy

Question

Still looking for help connecting your Kluwp account? Please contact our support team!