QuantaPayments

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant Key -> merchant_key (cannot be changed after the connection is created)
• Secret Key -> secret_key
• Api Url -> api_url (optional)
• Currency / Features / Method -> choose values available for your account (Method: payment_card)

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

QuantaPayments requires the customer's name, email, phone and full billing address (address, city, region, post code, country) for every payment. Provide them in the request, or set the matching Constants (see below) on the connection. If the customer's first and last name are not provided, the cardholder name is used.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "phone": "1234567890",
        "address": {
          "country": "MX",
          "region": "Mexico state",
          "city": "Mexico City",
          "full_address": "123 Main St.",
          "post_code": "12345"
        }
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "first_name": "John",
        "surname": "Smith",
        "email": "johnsmith@gmail.com",
        "phone": "1234567890",
        "address": {
          "country": "MX",
          "region": "Mexico state",
          "city": "Mexico City",
          "full_address": "123 Main St.",
          "post_code": "12345"
        }
      }
    }
  }
}

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.

After the successful connection, fill in constants for necessary routes in editing menu.

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 (if missing, the cardholder first name is used before the constant)
• last_name -> customer.surname (if missing, the cardholder last name is used before the constant)
• email -> customer.email
• phone -> customer.phone
• full_address -> customer.address.full_address (or customer.address.street)
• city -> customer.address.city
• region -> customer.address.region
• post_code -> customer.address.post_code
• country -> customer.address.country (ISO 3166-1 alpha-2, e.g. MX)