Solidgate

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Private Key
• Webhook Public Key
• Webhook Secret Key
• Save Instant Token -> must be explicitly set to true or false
• Google Pay MID (optional, for Google Pay)
• Apple Merchant ID (optional, for Apple Pay)
• Apple Display Name (optional, for Apple Pay)
• Apple Certificate (optional, for Apple Pay)
• Apple Certificate Password (optional, for Apple Pay)
• Test Mode -> (enable if you are using sandbox credentials)

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

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 - non-CVV sales aren't supported. Solidgate may return a 3D Secure challenge redirect depending on the card. Apple Pay and Google Pay are handled through Corefy's SDK the same way as on other connectors - no extra fields in the API request itself, just make sure the matching credentials above are set.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2d4e6f80-1a3b-4c5d-8e9f-0a1b2c3d4e5f",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

This connector also supports EUR, GBP, AUD, CAD, SGD, NZD, UAH.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "9c8b7a6f-5e4d-4c3b-2a1f-0e9d8c7b6a5f",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

customer is entirely optional - note that customer.email is the only customer field used for a card sale; if it's missing, Solidgate receives a placeholder test email address instead of nothing.

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

• finalize_by_protocol -> this toggle must be explicitly set (true or false) - if enabled, a sale that reaches the "3D Secure authenticated" stage is reported as successful immediately, instead of waiting for Solidgate's final capture/settlement confirmation.

Constants (fallback fields)

• instant_payment_type -> optional, enum (one_click / recurring / retry / installment / rebill) - classifies the type of stored-credential charge for a recurring request, per card network compliance rules; only used when charging a saved token, not on the original sale.

Recurring (save and charge a token)

If Save Instant Token is enabled on your connection, this connector supports saving the card as a token during a sale (via Corefy's standard tokenize-on-sale request) and later charging that same token without sending full card data again.

Refunds

Solidgate supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).