Skip to content

Logo

Libernetix

Your Money. Your Rules.

Supports in this guide: Payments

Provider website: libernetix.com

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

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

Prerequisites: get from Libernetix

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

  • API Key -> Corefy field api_key.
  • API Type -> Corefy field api_type -> Server to Server or Direct Post - check with your account manager which one your Libernetix account is set up for.
  • S2S Token (required if API Type is Server to Server) -> Corefy field s2s_token -> used instead of the API Key to authenticate card-submission requests in this mode.
  • Brand ID -> Corefy field brand_id.
  • Webhook Public Key (optional) -> Corefy field webhook_public_key -> used to verify callback notifications from Libernetix, if your account requires it.
  • API URL (optional) -> Corefy field api_url -> leave as default unless your account manager tells you otherwise.

Note

API Type controls how card data reaches Libernetix: with Server to Server, Corefy's own backend submits the card data to Libernetix; with Direct Post, the customer's browser/checkout layer submits it directly to Libernetix instead. Either way, you send requests to Corefy's API the same way - this only affects how card data travels behind the scenes.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • API Key
  • API Type
  • S2S Token (required if API Type is Server to Server)
  • Brand ID
  • Webhook Public Key (optional)
  • Strict Customer Data Validation (optional) -> see the important note under Options below
  • API URL (optional)

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

Success

You have connected Libernetix 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. Libernetix may return a classic (non-frictionless) 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
    }
  }
}

This connector also supports USD.

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",
        "individual_tax_id": "12345678901",
        "address": {
          "country": "FR",
          "region": "IDF",
          "city": "Paris",
          "full_address": "1 Main street",
          "post_code": "75000"
        }
      }
    }
  }
}

customer is entirely optional for a direct card sale - everything is only used to enrich the request.

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

  • fail_errors_on_sale -> optional, boolean, enabled by default - when Libernetix returns an ambiguous error status, this reports the sale as declined (final); disable it to have Corefy instead report it as a provider error, which your own logic can choose to retry.

Important

Strict Customer Data Validation (the connect-form field, multi-select) only applies to the follow-up status/charge step Corefy performs internally as part of processing - not to the fields you send directly in your payment-invoice request. customer.email is always required internally regardless of this setting. If you select specific fields here (Phone, Name, Street, Country, Individual Tax ID, City, Postcode, Region), make sure your customer data actually includes them, or transactions will fail with a validation error; select "None" to skip this extra check.

Refunds

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

Additional info

  1. Callback routing is automatic - Corefy generates the callback/return URLs per transaction, nothing to configure in Libernetix's own back-office.
  2. No payouts - this connector does not support payouts through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify API Key/S2S Token/Brand ID for the selected API Type and environment
  • Sale fails with a customer-data validation error -> check the Strict Customer Data Validation setting on your connection and make sure your customer data includes everything it requires
  • Not sure which API Type to pick? -> ask your Libernetix account manager which mode (Server to Server or Direct Post) your account is configured for
  • Refund fails on a second attempt -> only one refund is allowed per payment
  • Currency or service is not supported -> confirm allowed currencies/features in your Libernetix account and in Corefy

Question

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