Week Ending 2026-10-23

🚀 Now live: transaction expansions: GET /transactions and GET /transactions/{transactionId} accept expand=cardSubscription,card,cardholder, so you can read a transaction together with its card subscription, card and cardholder in one call.

🚀 New: platform-level card enrollment rule: Visa consumer debit and consumer prepaid cards are now refused at the network level, with a dedicated network_blocking_card error.


Production

Card Transactions

GET /transactions + GET /transactions/{transactionId}

  • You can now embed the card subscription, card and cardholder on a transaction with expand. Any combination of cardSubscription, card and cardholder can be requested together; each is returned under _embedded as a sibling (_embedded.cardSubscription, _embedded.card, _embedded.cardholder) and reflects the resource as it is now, not a snapshot from transaction time. Each value needs its matching read scope (card-subscriptions:read, cards:read, cardholder:read); a missing scope returns 403. An embed key is present only when requested and the resource exists, never null. Responses without expand are unchanged. Transaction webhooks can carry the same embeds; this is enabled per account and off by default.
  • ⚠️ Breaking: expand on GET /transactions/{transactionId} is now validated. It was previously ignored, so an unknown value now returns 400.

transaction.created / transaction.updated webhooks + GET /transactions

  • Transactions now carry controlAccountNumber on American Express transactions. This is the Amex Basic Control Account number for the card, as supplied by the Amex feeds. Treat it as an opaque string and keep it exactly as returned (it can contain leading zeros). It is present only on Amex transactions where the feed supplies it, and absent otherwise.
  • Transactions now return networkBulkFeedId. It was already documented on the transaction but was not being returned; it is now returned on the API and the transaction webhooks. It is absent when unknown, never null or empty.

Card enrollment

POST /card-subscriptions

  • ⚠️ Breaking: Visa consumer debit and consumer prepaid cards are now refused at the network level. These cards are rejected with a 403 and the new error code card_subscription.network_blocking_card (for example This card is not supported on this network (CONSUMER DEBIT card)), checked before any account or subaccount block rules. The rule is set by Astrada and is not configurable per account or subaccount; consumer credit cards remain configurable through your existing block settings. Subaccount reads (GET, list, and the POST/PATCH responses) now include a read-only networkBlockedCards map, keyed by network, listing the rules that apply to single and bulk enrollment. Card Enrollment SDK 1.56.0 shows cardholders a dedicated message for this error, with a Start over button.

POST /enrollment-methods

  • A temporary Mastercard lookup failure no longer grades a card as not bulk-eligible. Previously an outage on the Mastercard BIN service was reported as bulkLikelihood: none, so a bulk-capable program could look single-only. A definitive "BIN not found" still grades none; other failures now return a retryable error instead of a verdict.

cardholder.updated webhook

  • The cardholder.updated payload now includes corporate.networkToken for tokenized Amex cards, the same way GET /cards/{cardId}/cardholder returns it, so you can match the cardholder to its card without an extra read. Cards without a network token get no key.

Amex file-based bulk enrollment

POST /network-bulk-feeds

  • Amex bulk feeds can now be created with your 6-digit Amex Company ID (CID) as the networkReference in production. Previously production only accepted the recipient ID form (R<number>), and the CID form was sandbox-only. Both forms are now accepted in every environment, and files delivered under your recipient ID are matched to a CID-keyed feed. Invalid values return Expected 'R<number>' or a 6-digit companyId.