Fibonatix

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Login -> (your Fibonatix merchant login)
• Control Key -> (secret used to sign requests and validate callbacks)
• Endpoint ID -> (your Fibonatix terminal/endpoint identifier)
• API URL -> (optional - override the default production URL; not used in test mode)
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. You can set these parameters according to available currencies and features for your Fibonatix account, but it is necessary to check details of the connection with your Corefy account manager.

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8f3c2a71-5d4e-4b9a-a6c1-2e7f0d9b4c35",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "3b9e6d12-7a4f-4c08-9e5b-c1d2a8f7e604",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "c7a51e09-2f8b-4d3c-b6e4-90d1f2a3b578",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+4930123456789",
        "date_of_birth": "1990-05-14",
        "address": {
          "country": "DE",
          "region": "BE",
          "city": "Berlin",
          "post_code": "10115",
          "full_address": "Invalidenstrasse 1"
        }
      }
    }
  }
}

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 (3)

• ignore_callback - stops Corefy from processing callbacks received from Fibonatix
• use_default_browser_info - fills in missing browser/device data from the BROWSER_* constants
• custom_finalization_logic - prevents an approved response from being treated as an error because it also carries an error code

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)

• ADDRESS -> customer.address.full_address / customer.metadata.address
• CITY -> customer.address.city / customer.metadata.city
• POST_CODE -> customer.address.post_code / customer.metadata.zip
• COUNTRY -> customer.address.country / customer.metadata.country (ISO 3166-1 alpha-2, e.g. DE)
• PHONE -> customer.phone
• EMAIL -> customer.email
• DATE_OF_BIRTH -> customer.date_of_birth (constant format YYYYMMDD, e.g. 19900514)
• BROWSER_INFO, BROWSER_TZ_OFFSET, BROWSER_SCREEN_WIDTH, BROWSER_SCREEN_HEIGHT, BROWSER_COLOR_DEPTH, BROWSER_LANGUAGE, BROWSER_JAVA_ENABLED, BROWSER_ACCEPT_HEADER, BROWSER_USER_AGENT, BROWSER_IP -> customer browser/device data; only used when the use_default_browser_info option is enabled