Week Ending 2026-10-16

🚀 Now live: cardholder.updated webhook: get notified when a card's cardholder details change, instead of re-polling GET /cards/{cardId}/cardholder.


Production

cardholder.updated webhook (new)

  • You can now subscribe to cardholder.updated to learn when a card's cardholder changes. The event fires only on a real change to the cardholder details, whether it came from the card network (for example an issuer changing an employee ID in a daily card file) or through the API. It does not fire when a cardholder is first created, or when the network resends identical data. The payload is the cardholder resource (name, email, postal code, corporate identifiers) plus cardId, accountId, subaccountId and _links to the cardholder and the card. The event is opt-in: add cardholder.updated to a webhook's event types via POST /webhooks or PATCH /webhooks/{webhookId}. Existing webhooks are unaffected. Delivery is best effort.

GET /cards and GET /cards/{cardId}

  • You can now embed the cardholder on card reads with expand=cardholder, and filter the card list by networkBulkFeedId. expand=cardholder embeds the cardholder under _embedded.cardholder on each returned card, with the same body as GET /cards/{cardId}/cardholder, and requires the cardholder:read scope (a token without it gets a 403 Missing scope 'cardholder:read'). The cardholder key is absent, not null, when a card has no cardholder. A repeated, empty or unknown expand value returns a 400. GET /cards?networkBulkFeedId=<id> returns cards with a live subscription on that feed; an unknown feed id returns an empty page. Pagination links keep both parameters, and responses without expand are unchanged.

POST /enrollment-methods

  • Mastercard eligibility lookups now use every BIN digit you send, up to 11. More digits give a more precise match against Mastercard's account ranges. When several ranges come back, the one containing your BIN prefix is used rather than grading the card as not bulk-eligible.

Sandbox

Step-by-step transaction simulation

  • You can now drive a sandbox transaction one message at a time. POST /simulate/transactions starts a transaction on an enrolled card (type: authorization or settlement), and POST /simulate/transactions/{transactionId} adds the next step (authorization, adjustment, reversal, settlement or refund). Each call publishes a single message and returns 202 with its messageId, so you can observe each transaction.created / transaction.updated webhook in turn. A step that doesn't fit the current hold (for example a reversal when nothing is on hold) returns 409. Requires simulation:write plus the read scopes listed in the Sandbox guide.