Moneliq

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Login
• Password
• API URL
• Terminal (optional)
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features; 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. Moneliq 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_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "address": {
          "country": "FR"
        }
      }
    }
  }
}

This connector also supports USD, GBP, CZK, DKK, HUF, ISK, CHF, NOK, PLN, RON, SEK.

Payment - MAX

POST /api/payment-invoices

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

customer.name, when sent, is automatically transliterated to Latin before being sent to Moneliq.

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

• time_to_finalize -> optional, number (hours) - if a reconciliation check still shows the payment pending this many hours after it was created, Corefy gives up waiting and reports it as a timed-out failure instead of checking indefinitely.
• pending_on_validation_failure -> optional, boolean - when a sale fails Moneliq's own validation, reports it as pending (requiring reconciliation) instead of a final decline.

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 describe the customer's device/browser (used for fraud checks and 3D Secure) and the Terminal field - not customer address or contact details, which have no fallback here.

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 -> a built-in default is used (a generic Windows/desktop browser profile) for device/browser fields

Currently available constants (constant -> Corefy API field)

• OS -> device operating system; defaults to Windows if not set
• OS_VERSION -> OS version/architecture; defaults to x86_64 if not set
• PLUGINS -> browser plugin list; defaults to a generic PDF-viewer plugin list if not set
• IS_MOBILE -> whether the device is mobile; defaults to false if not set
• TERMINAL -> fallback for the Terminal connection field, if your account uses one

Refunds

Moneliq supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Login
• Password
• Terminal (optional)
• API URL (optional)
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to a Moneliq-hosted page to complete the payment with card, Apple Pay, or Google Pay. The exact methods/currencies available depend on what's enabled for your specific account - check with your account manager.

Payment - MIN

POST /api/payment-invoices

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

customer is entirely optional - everything is only used to prefill the hosted form, it never blocks the sale.

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 flow.

Options

• force3d -> optional, boolean - forces every sale through 3D Secure, instead of leaving the decision to Moneliq/the card's own risk assessment.

Refunds

This flow does not support refunds - use the H2H Merchant account if you need refunds.