MatrixPaySolution

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Public Key
• Secret Key
• API URL (optional)
• 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. Apple Pay and Google Pay use the same H2H flow as card - no separate merchant IDs or certificates needed.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "3c4d5e6f-7a8b-4c9d-8e02-3f4a5b6c7d8e",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "4d5e6f7a-8b9c-4d0e-8f13-4a5b6c7d8e9f",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "US",
          "city": "New York",
          "full_address": "1 Main street",
          "post_code": "10001"
        }
      }
    }
  }
}

customer is entirely optional. For the cardholder name, the priority is the name embossed on the card, 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

Options

• customer_traffic_type -> optional, enum (trusted, untrusted) - classifies the customer's traffic for MatrixPaySolution's own risk scoring; overridden per-request if you send customer.metadata.customer_labels.

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
• address -> customer.address.full_address
• city -> customer.address.city
• country -> customer.address.country
• zip -> customer.address.post_code
• state -> fallback for the state field described above (normally sourced from customer.address.country, not region)
• ip -> customer.metadata.ip

Refunds

This connector does not support refunds.