Sent when a card authorisation needs a decision (e.g. a 3-D Secure challenge) and again as the authorisation is resolved. Carries a trimmed cardAuthentication object. All deliveries share the common envelope (eventId, eventName, timestamp, customerId), plus payloadVersion (2).

cardAuthentication fields

Only id, customerId and status are guaranteed. Every other field is included only when known, so absent fields are omitted rather than sent as null. If an amount can’t be stated exactly, amount and currency are both omitted.
On some card programmes cardId is not the Orenda card id (match on customerId, accountId, amount and merchant), maskedPan is not sent, and statuses run pending → approved / rejected → the scheme outcome. In sandbox the scheme outcome is not sent. See the card transactions guide (available from client.support@orenda.finance), or contact the team if you are unsure which applies.
Integrations created before this format was introduced receive the original payload: there is no payloadVersion field, amount is a number in the card programme’s own unit (some programmes send major units, others minor units), and currency may be a numeric code. We recommend moving to the format above, and we will contact you before anything changes for your programme. Ask us which format you receive.

Example