FMPay

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Login
• Password
• API URL
• Save OCT token -> (optional) enable so refunds don't require card data again
• 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. CVV is always required. FMPay may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "4046efc0-aed7-4276-a86f-fc2876b45143",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "96d4e629-4c12-4832-9be8-f7753b89d200",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "john@example.com",
        "phone": "+380999999999",
        "address": {
          "country": "SE"
        }
      }
    }
  }
}

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. These are device/browser metadata fields, not customer data.

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)

• OS -> device operating system
• OS_VERSION -> device operating system version
• PLUGINS -> browser plugins list
• IS_MOBILE -> whether the customer's device is mobile

Refunds

FMPay supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment). Refunds don't require card data again - the connection relies on a token saved at the time of the original sale.