Skip to content

Logo

Leikur

A corporate banking service for global internet and game-tech industries. Finally.

Supports in this guide: Payments

Provider website: leikur.com

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

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

Prerequisites: get from Leikur

Contact your Leikur account manager (or apply at leikur.com/#six) to get your account verified and receive the following credentials.

  • Merchant ID -> Corefy field merchant_id.
  • API key -> Corefy field api_key.
  • Secret key -> Corefy field secret_key.

Available currencies and features depend on your Leikur account - confirm with your account manager which services/currencies apply to your setup.

Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Merchant ID
  • API key
  • Secret key
  • Currency / Features -> choose the values available for your account

Success

You have connected Leikur 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. CVV is always required (non-CVV payments are not supported) and 3DS version control is not configurable for this connector.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6f7a8b9c-0d1e-4f2a-8b13-6c7d8e9f0a1b",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 21
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "7a8b9c0d-1e2f-4a3b-8c24-7d8e9f0a1b2c",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 21,
      "customer": {
        "reference_id": "c4456386-ced2-4ba2-9a05-b55eab866567",
        "name": "John Doe",
        "email": "test@mail.com",
        "date_of_birth": "1990-01-01",
        "address": {
          "full_address": "Baker street 221B",
          "country": "GB",
          "city": "London",
          "post_code": "12345"
        }
      }
    }
  }
}

Important

customer.name is split into first/last name parts. If a customer field is missing, the matching Constant (if set) is used instead; if neither is present, that field is simply not sent.

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 - relies only on an active status request (reconciliation) to finalize the payment, instead of also allowing the asynchronous callback to do so; useful when cascading to another connector so a decline is known right away rather than waiting on a callback that may never arrive.

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)

  • FIRST_NAME -> customer.name (first part)
  • LAST_NAME -> customer.name (second part)
  • DATE_OF_BIRTH -> customer.date_of_birth
  • EMAIL -> customer.email
  • FULL_ADDRESS -> customer.address.full_address
  • CITY -> customer.address.city
  • POST_CODE -> customer.address.post_code
  • COUNTRY -> customer.address.country

Refunds

Leikur does not support refunds.

Additional info

  1. Active reconciliation is available - besides the asynchronous callback, Corefy can also request the payment status directly from Leikur, unless ignore_callback changes how finalization is handled.
  2. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the Merchant ID, API key and Secret key
  • Payment fails with missing cardholder data -> send customer.name, customer.email, customer.date_of_birth and customer.address fields, or configure the matching Constants as a fallback
  • Currency or service is not supported -> confirm allowed currencies/features in your Leikur account and in Corefy
  • Refund request fails -> Leikur does not support refunds at all

Question

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