Fingenom

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Secret key
• API URL (optional)
• Currency / Features -> choose values available for your account (EUR, USD, GBP, AUD, CAD)
• Test Mode -> (enable if you are using sandbox credentials)

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. Fingenom may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "34779d6e-9e99-49b9-86a9-a7cc52482f09",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 5
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "9c9c2ad0-5b1a-4e3f-8d12-1a2b3c4d5e6f",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 5,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "john@example.com",
        "phone": "+380999999999",
        "date_of_birth": "1998-06-16",
        "address": {
          "full_address": "Main street 1",
          "country": "UA",
          "region": "Kyiv",
          "city": "Kyiv",
          "street": "Main street 1",
          "post_code": "10028"
        }
      }
    }
  }
}

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

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)
• EMAIL -> customer.email
• PHONE -> customer.phone
• COUNTRY -> customer.address.country
• REGION -> customer.address.region
• STREET -> customer.address.street
• CITY -> customer.address.city
• POST_CODE -> customer.address.post_code
• DATE_OF_BIRTH -> customer.date_of_birth

Refunds

Fingenom does not support refunds.