GateIQ

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

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

Choose Currency / Features; check with your Corefy account manager which methods are enabled for your account.

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to a GateIQ-hosted page to complete the payment. Available methods - BLIK, Apple Pay, Google Pay, Revolut Bank, bank transfer, Paysafecard, PaySkin, Tether, N26 Bank, Wise, Skrill, Neteller, EPS, Rapid Transfer - depend on what's enabled for your account.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1d2e3f40-5a6b-4c7d-8e91-2f3a4b5c6d7e",
      "service": "blik_pln_hpp",
      "currency": "PLN",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2e3f4a51-6b7c-4d8e-8f02-3a4b5c6d7e8f",
      "service": "blik_pln_hpp",
      "currency": "PLN",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-05-20",
        "address": {
          "country": "PL",
          "city": "Krakow",
          "full_address": "1 Main street",
          "post_code": "30-001"
        },
        "metadata": {
          "kyc_verified": "true"
        }
      }
    }
  }
}

customer is entirely optional - everything is only used to prefill the hosted form, it never blocks the sale. customer.metadata.kyc_verified ("true"/"false") tells GateIQ whether you've already KYC-verified this customer yourself.

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

• collect_merchant_url_from_metadata -> optional, boolean - by default, GateIQ receives your website URL from your Corefy merchant profile (or the website_url Constant as a fallback); enable this to instead take it from metadata.merchant_url in the request, falling back to the usual source if that's missing.

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)

• email -> customer.email
• phone -> customer.phone
• first_name -> customer.name (first part)
• last_name -> customer.name (second part)
• country -> customer.address.country
• city -> customer.address.city
• full_address -> customer.address.full_address
• post_code -> customer.address.post_code
• date_of_birth -> customer.date_of_birth
• website_url -> your website URL, see the collect_merchant_url_from_metadata option above for the full priority.

Refunds

This connector does not support refunds.