Week Ending 2026-09-04

Production

Card Subscriptions

GET /card-subscriptions

  • You can now filter the subscription list by bankAccountId. Subscriptions whose card was created from a bank connection carry a bankAccountId; passing it as a query parameter returns only the cards that came from that bank account. It combines (AND) with the existing subaccountId, cardId, state and networkBulkFeedId filters. A value that is not a valid UUID returns a 400.

POST /enrollment-methods

  • The response now includes the card issuer's name. An optional binInfo.issuerName is returned alongside the eligibility verdict, so you can show or store the issuing bank without calling GET /bin-lookup (which needs the cards:read scope). It is best-effort: if the issuer name can't be determined, binInfo is omitted and the eligibility result is unaffected. The Unified Enrollment SDK carries the same binInfo.issuerName on the bulk-enrollment feed-created event and the onSuccess payload.

transaction.created / transaction.updated webhooks

  • Embedded messages now carry the Amex traceId. Each entry in _embedded.messages[] gains traceId, the Amex reconciliation reference. It is populated for Amex and null for every other network. Previously this value was only on the transactionmessage.created payload, so Amex integrators consuming only transaction webhooks can now reconcile without subscribing to message events. This is additive.

POST /network-bulk-feeds

  • ⚠️ Breaking: panFormat is now rejected on feed creation outside the Sandbox. panFormat is a read-only field on feed responses. It was previously ignored if sent on POST /network-bulk-feeds; it now returns a 400. If you round-trip a feed resource back into a create request, remove panFormat first.

Unified Enrollment SDK

  • Bulk + bank configurations no longer dead-end on cards that aren't bulk-eligible. When the card rail is off and bank linking is on (cardEnrollment: false, bankEnrollment: 'on'), a card that can't be bulk-enrolled now falls through to bank linking instead of stopping on the "This card can't be enrolled here" screen. In this configuration the card field also accepts just the BIN rather than a full card number, with the minimum digit count configurable via the new minBinDigits option.

Sandbox

Card enrollment

  • Visa test cards can now be enrolled through single-card enrollment. Enrolling a published Visa sandbox test card previously failed with a 500; it now completes like the Mastercard test cards do.
  • New Sandbox subaccounts no longer need verificationPolicy.sandbox: true to enroll test cards. In the Sandbox environment, single-card enrollment now runs in sandbox mode automatically, so POST /card-subscriptions works on a fresh subaccount without first patching its verification policy. Only published test cards are accepted.
  • The SDK card field no longer enforces the Luhn check in the Sandbox. You can drive the enrollment flow with a made-up (but complete) card number. Production still enforces the full check, and a BIN on its own is still not accepted in any environment.

POST /simulate/transaction/scenario

  • Seven new ride-share scenarios are available. The scenario field now accepts uber_canada_reversal, uber_netherlands_positive_advice, uber_turkey_dual_auth, uber_brazil_cancelled, uber_korea_settle_at_auth, uber_turkey_fx_reversal and uber_india_fx_clearing, covering multi-country reversals, advices, dual authorizations, cancellations and foreign-exchange flows. Previously these keys were rejected with a 400.

Amex bulk enrollment simulation

  • Amex feeds can now be simulated with tokenized card numbers. POST /network-bulk-feeds accepts panFormat (encrypted | tokenized) for Amex feeds in the Sandbox only. When the feed is tokenized, the Amex simulate-ingestion endpoint draws from the published tokenized Amex test cards, and the enrolled cardholder carries corporate.networkToken. A tokenized feed currently enrolls up to 2 cards, and newCardCount is rejected with a 400 on a tokenized feed.
  • The default simulated cardCount for encrypted Amex feeds changes from 5 to 3. Tokenized feeds default to 2. Pass cardCount explicitly if you depend on a specific number.
  • Amex feeds can be keyed on the 6-digit company ID. In the Sandbox, the Amex networkReference on POST /network-bulk-feeds and on the simulate-ingestion endpoint accepts either the recipient ID (R followed by digits) or the 6-digit Amex company ID. Production still requires the recipient ID form.
  • Simulated Amex cardholders now include company and employee identifiers and an email. Sandbox Amex cardholders are populated with corporate.id (the company ID), corporate.alternativeEmployeeId and a synthetic email, matching the shape of Visa and Mastercard bulk cardholders.