Worldline identifier availability depends on the product, payment method, and API used. Confirm the online field paths below for your integration; they are not available across every Worldline product or terminal.
For the integrated online payment flow, read PAR from paymentOutput.cardPaymentMethodSpecificOutput.paymentAccountReference when supplied. A callback may omit the details; retrieve the payment from Worldline to check whether the payment itself includes them.
Pass an available PAR to IdentificationDetails.cardDetails.paymentAccountReference during recipient resolution. Automatic delivery requires a match to a Cheqi user.
Terminals: PAR availability for terminal integrations is not verified here. Confirm the response field, account requirements, and timing for your specific Worldline product and API before relying on automatic card matching.
For supported online redirect bank payments, such as iDEAL, read the customer's IBAN from paymentOutput.redirectPaymentMethodSpecificOutput.customerBankAccount.iban when it contains the full value. Retrieve the payment if the callback omits these details. The presence of this field depends on the product and payment method; a masked value or suffix is not sufficient for automatic matching.
Pass a full IBAN to IdentificationDetails.paymentAccountDetails.identifier, with accountIdentifierType: "IBAN". IBAN availability for in-store terminal payments has not been verified here.
Worldline supports last-four card details. Include them 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 for the required receipt input, or return to Payment Provider Compatibility for coverage across providers.