Payment provider compatibility

Use an available card Payment Account Reference (PAR) or full customer IBAN for automatic receipt delivery. Include last four card digits in the encrypted receipt when available, and offer the enabled web wallet link when no customer matches.

Identifier availability depends on the provider, payment method, channel, account settings, and individual transaction. A terminal model alone does not establish which identifiers your integration receives. A debit card payment does not by itself mean the provider exposes the customer's IBAN.

Choose a matching path

Identifier	How it is used	Where to send it
Card PAR	Automatic matching to a Cheqi user during recipient resolution	`IdentificationDetails.cardDetails.paymentAccountReference`
Full customer IBAN	Automatic matching to a Cheqi user during recipient resolution	`IdentificationDetails.paymentAccountDetails.identifier`, with `accountIdentifierType: "IBAN"`
Last four card digits	Receipt payment metadata; cannot identify a customer at checkout	Encrypted `ReceiptPayload.paymentDetails.cardLastFour`

PAR and IBAN delivery require a successful recipient match. Four digits alone cannot identify a customer at checkout.

Provider coverage

Availability varies by account and transaction. Confirm the required fields with your provider and test your integration. This table does not certify terminal models; unverified coverage is identified below.

Card payments: PAR

Provider and channel	PAR availability	Required action or limitation
Adyen terminals (Terminal API)	Available when enabled, if supplied for the transaction	Enable PAR in the Adyen Customer Area.
Adyen online cards	Available when enabled, if supplied for the transaction	Enable PAR in Additional data and in standard webhooks when using that path.
Stripe Terminal	Request account enablement	Follow Enable PAR in Stripe for `card_present` payments.
Stripe online cards	Request account enablement	Follow Enable PAR in Stripe, including `charge.updated` events for later PAR updates.
Mollie terminals	Unverified with a live payment	Use the card fingerprint only when it contains a valid PAR.
Mollie online cards	Current availability unverified	Confirm current PAR availability with Mollie before relying on card matching.
Worldline terminals	Unknown for the terminal integration	Confirm PAR availability for your specific Worldline product and API.
Worldline online cards	Read when supplied by the integrated online API	Read PAR from the payment, retrieving it when missing from the callback.

Bank payments: IBAN

Use the customer's full IBAN returned for the payment. A masked IBAN, an IBAN suffix, a domestic account number, or the merchant's receiving account must not be supplied as the customer's full IBAN.

Provider and payment flow	Full customer IBAN availability	Required action or limitation
Adyen online bank payments, such as iDEAL	Used when returned for the account and payment	Ask Adyen to include customer bank details if they are missing.
Mollie online bank payments, such as iDEAL	Used when `details.consumerAccount` contains a full IBAN	Validate the account type; this field can contain other account references.
Worldline online redirect bank payments, such as iDEAL	Used when the integrated online API returns a full IBAN	Retrieve the payment when the callback omits bank details. Availability depends on the product and payment method.
Stripe online bank payments, including iDEAL and SEPA Direct Debit	Suffix-only responses cannot support full-IBAN matching	Use another matching identifier or offer the QR receipt. PAR enablement does not establish IBAN availability.

Verify full-IBAN availability for your account and payment method. IBAN availability for in-store terminal payments is not verified here.

“Unknown” and “unverified” do not mean a provider cannot expose the identifier. An unavailable status applies only to the specific product, channel, or test described.

For other providers or payment methods, confirm which customer identifiers the API exposes, whether account enablement is needed, and when the identifiers become available.

QR collection with the last four card digits

Adyen, Stripe, Mollie, and Worldline support last-four card details for card payments. This gives your integration a QR collection path even when PAR is missing or automatic matching finds no customer.

Include the last four card digits in the definitive encrypted receipt's paymentDetails.cardLastFour field. For example, this fragment belongs in ReceiptPayload before encryption:
```
{
  "paymentDetails": {
    "cardLastFour": "4242"
  }
}
```
Offer the web wallet link as a QR code when download fallback is enabled.
The customer opens the link in their browser or collects the receipt in the Cheqi app. Checkout does not need to wait for collection.

Do not put last-four card digits in IdentificationDetails.cardDetails or pass a provider-specific fingerprint as paymentAccountReference. The suffix belongs in the encrypted receipt.

When no automatic match is available

Continue recipient resolution with another appropriate identifier, such as a customer's pairing code, a supported payment-account identifier, or their Cheqi email address. If no customer matches and download fallback is enabled, offer the web wallet link, for example as a QR code at checkout. If no delivery route is available, continue with your existing receipt process.

For a card payment without PAR or another reliable customer identifier, keep paymentType in the identification request and include the last four digits in the encrypted receipt as described above. An IBAN suffix is not a card suffix and must not be placed in cardLastFour.

See card-payment receipt metadata and Download Links for the fallback flow.

Provider guides

The provider subpages contain setup instructions, response fields, and the availability limitations for each integration: