Week Ending 2026-10-16
about 1 month ago
🚀 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)
cardholder.updated webhook (new)- You can now subscribe to
cardholder.updatedto 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) pluscardId,accountId,subaccountIdand_linksto the cardholder and the card. The event is opt-in: addcardholder.updatedto a webhook's event types viaPOST /webhooksorPATCH /webhooks/{webhookId}. Existing webhooks are unaffected. Delivery is best effort.
GET /cards and GET /cards/{cardId}
GET /cards and GET /cards/{cardId}- You can now embed the cardholder on card reads with
expand=cardholder, and filter the card list bynetworkBulkFeedId.expand=cardholderembeds the cardholder under_embedded.cardholderon each returned card, with the same body asGET /cards/{cardId}/cardholder, and requires thecardholder:readscope (a token without it gets a403Missing scope 'cardholder:read'). Thecardholderkey is absent, notnull, when a card has no cardholder. A repeated, empty or unknownexpandvalue returns a400.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 withoutexpandare unchanged.
POST /enrollment-methods
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/transactionsstarts a transaction on an enrolled card (type: authorizationorsettlement), andPOST /simulate/transactions/{transactionId}adds the next step (authorization,adjustment,reversal,settlementorrefund). Each call publishes a single message and returns202with itsmessageId, so you can observe eachtransaction.created/transaction.updatedwebhook in turn. A step that doesn't fit the current hold (for example a reversal when nothing is on hold) returns409. Requiressimulation:writeplus the read scopes listed in the Sandbox guide.
