MatrixPay

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Secret Key
• Test Mode -> (enable if you are using sandbox credentials)

Corefy doesn't restrict currencies for this connector in advance - available currencies depend entirely on what's enabled for your MatrixPay account; confirm with your account manager.

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.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "5e7f9a12-3c4d-4e6f-8a01-9b2c3d4e5f6a",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6f8a0b23-4d5e-4f7a-9b01-0c3d4e5f6a7b",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-05-20",
        "individual_tax_id": "12345678900",
        "passport_number": "AB123456",
        "address": {
          "country": "DE",
          "region": "Bavaria",
          "city": "Munich",
          "full_address": "1 Main street",
          "post_code": "80331"
        }
      }
    }
  }
}

customer is entirely optional. For first/last name, Corefy prioritizes customer.first_name/customer.surname if sent, then falls back to splitting customer.name, then the Constants below.

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 Options are configured for this connector.

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.first_name (falls back to the first part of customer.name)
• last_name -> customer.surname (falls back to the second part of customer.name)
• date_of_birth -> customer.date_of_birth
• full_address -> customer.address.full_address
• city -> customer.address.city
• region -> customer.address.region
• post_code -> customer.address.post_code
• country -> customer.address.country
• email -> customer.email
• phone -> customer.phone
• individual_tax_id -> customer.individual_tax_id
• passport_number -> customer.passport_number
• reference_id -> customer.reference_id

Refunds

This connector does not support refunds.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Secret Key
• 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 MatrixPay-hosted page to complete the payment. Card and bank transfer methods are available depending on what's enabled for your account.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "7a9b1c34-5e6f-4a8b-9c01-1d4e5f6a7b8c",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8b0c2d45-6f7a-4b9c-8d01-2e5f6a7b8c9d",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-05-20",
        "individual_tax_id": "12345678900",
        "passport_number": "AB123456",
        "address": {
          "country": "DE",
          "region": "Bavaria",
          "city": "Munich",
          "full_address": "1 Main street",
          "post_code": "80331"
        }
      }
    }
  }
}

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 Options are configured for this flow.

Constants (fallback fields)

Same priority rule and field list as the H2H Merchant account above, configured per payment method/service.

Refunds

This connector does not support refunds.