Shift4 EU

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Secret Key
• Save Instant Token (optional)
• 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. Shift4 supports full 3D Secure 2 - depending on the card and your account's liability-shift settings (see Options below), Shift4 may return a 3D Secure challenge redirect.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

This connector also supports USD, JPY, GBP.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

customer is normally optional, with one exception - see the important note 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 Constants are configured for this connector.

Options

• stored_credential_mode -> optional, enum (none / recurring / unscheduled) - tells Shift4 what kind of stored-credential charge this is, per card network compliance rules: recurring for subscription-style recurring charges, unscheduled for customer- or merchant-initiated charges on file that don't follow a fixed schedule. Used together with Save Instant Token.
• charge_on_bypassed_liability_shift -> optional, boolean - after a 3D Secure challenge, allows the charge to proceed even when Shift4 reports the liability shift as "bypassed" (3DS wasn't actually performed), instead of declining it.
• charge_on_not_possible_liability_shift -> optional, boolean - allows the charge to proceed when Shift4 reports that a liability shift wasn't possible for this card, instead of declining it.
• charge_on_failed_liability_shift -> optional, boolean - allows the charge to proceed even when the 3D Secure liability shift itself failed, instead of declining it.

Recurring (save and charge a token)

If Save Instant Token is enabled on your connection, this connector registers the customer's card with Shift4 on the first sale (requires customer.email, see above) and lets you charge that saved card again later via Corefy's standard recurring request, without resubmitting full card data.

Refunds

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