# Enable PAR in Stripe

Cheqi can use a card's Payment Account Reference (PAR) to match a payment to a
Cheqi user for automatic receipt delivery. Request
access for the Stripe account that processes your payments, covering both
online cards and Stripe Terminal (`card_present`) if you use both.

## Request account enablement

1. Log in to the Stripe account that processes your payments.
2. Open [Stripe Support](https://support.stripe.com/contact) and start a chat.
3. Paste the message below. If the chat opens with an AI assistant, ask to
speak to a person.
4. Ask Stripe to confirm enablement for your account and payment channels.
Once enabled, check that eligible new card payments return PAR.


Message to copy:

```text
Hi, can I talk to a human about enabling a feature on our account?

We would like the Payment Account Reference (PAR) to be available on the charge object for our Stripe account, for both online card payments and Stripe Terminal (card_present) payments.

We use PAR to automatically deliver digital receipts to our customers with Cheqi.

Could you submit a request to enable this for our account?
```

## Receive PAR in your integration

Stripe exposes PAR on the Charge object, and it can arrive after the payment
succeeds. [Stripe's PAR walkthrough](https://stripe.com/nz/sessions/2026/tracking-customer-spend-across)
demonstrates receiving it through `charge.succeeded` and `charge.updated`.
Subscribe to `charge.updated` if your integration needs to handle a later PAR
update. Use your integration's webhook handling instructions for the endpoint
and receipt-delivery behavior.

Pass an available PAR to
`IdentificationDetails.cardDetails.paymentAccountReference` during
[recipient resolution](/receipts/recipient-resolution). Account enablement does not
guarantee every payment will have a PAR, and automatic delivery still requires
a match to a Cheqi user. Checkout should continue without waiting for PAR.

## When PAR is unavailable

Include the last four card digits in the encrypted receipt's
`ReceiptPayload.paymentDetails.cardLastFour` and offer the receipt QR code when
download fallback is enabled. See
[QR collection with the last four card digits](/receipts/payment-provider-compatibility#qr-collection-with-the-last-four-card-digits).

## Full IBAN for bank payments

PAR enablement applies to card payments. Bank-payment responses may contain
only a suffix, such as `iban_last4` or `last4`. These cannot identify the
customer for automatic IBAN matching. Use another matching identifier or
offer the QR receipt when download fallback is enabled.

Only supply `IdentificationDetails.paymentAccountDetails.identifier` with
`accountIdentifierType: "IBAN"` when you have the customer's full IBAN. An IBAN
suffix is not a card suffix and must not be placed in `cardLastFour`. See
[Payment Provider Compatibility](/receipts/payment-provider-compatibility) for card
and bank-payment coverage.