Week Ending 2026-10-30

🚀 Now available: Unified Enrollment SDK v2: every session starts on the card number and the SDK routes each card by its program and by who is on the page. v2 is served from /unified/v2; /unified/v1 keeps serving v1, so you move when you choose.


Production

Cardholder

GET /cards/{cardId}/cardholder, expand=cardholder + cardholder.updated webhook

  • Amex bulk-enrolled cards now carry their Company ID as corporate.id in production. The 6-digit Corporation ID from the Amex card file is now set on the cardholder in every environment (previously sandbox only). Rows without a valid ID leave corporate.id out.

Card Transactions

  • Visa push credits now settle at the credited amount instead of 0. A push credit arrives as a positive request confirmed by a matching negative return; the pair was netting to a settled amount of 0. It now settles as a single transaction with a negative settled amount equal to the credit, whatever your refund-correlation setting. This applies to new transactions going forward. Visa return messages are also now timestamped at the end of the day they are received, the same convention as other clearing messages, so they sort after the purchase they reverse.

POST /enrollment-methods

  • 6-digit Mastercard BINs are graded again. Since mid-October, lookups with a 6-digit Mastercard BIN were rejected before reaching Mastercard, so they were graded bulkLikelihood: none or returned an error. 6- and 7-digit BINs are now sent as-is; up to 11 digits are still used when you send them.
  • When Mastercard BIN data is unavailable, you now get a degraded answer instead of an error. The lookup is retried once, then graded from static BIN data with bulkLikelihood capped at medium (a proven program stays proven). When nothing can decide the grade, the response is a 200 with bulkLikelihood omitted, a new optional unavailable field listing it, singleEligible: true and only cardholder-single offered. A none grade is only returned when it was actually established.

GET /bin-lookup

  • Two Mastercard BINs are now correctly classified as corporate credit. They were labeled consumer in the reference data; type and cardCategory now return CORPORATE.

Network Bulk Enrollments

POST /network-bulk-enrollments

  • The bulk enrollment kickoff accepts an idempotency key, a card count and new dedicated scopes. An optional requestId (uuid, unique per account) makes retries safe: repeating a request with a requestId you already used returns the stored enrollment with 200 instead of creating a second one. An optional cardCount (1 to 1,000,000) sets the stored cardCountBand for you; sending only cardCountBand still works. The kickoff now accepts the network-bulk-enrollments:write and network-bulk-enrollments:read scopes, and tokens holding only the network-bulk-feeds scopes are still accepted.

Network Bulk Feeds

  • A feed's updatedAt now reflects its last change. GET, the feed list and the networkbulkfeed.statechanged webhook previously kept reporting the creation time. Existing feeds update on their next change. A late failure event also no longer puts a stale errorReason on a feed that is already ACTIVE.
  • Re-registering a Visa file-based program after its previous feed failed or was deactivated now works. The new feed was being handed the old feed's inactive link, so its files were held and the feed never activated. The link is now re-pointed at the new feed, and files held while it was inactive are released straight away.

Banking

POST /bank-links

  • Refused bank link creates now carry a stable code, and an unknown subaccount is refused. A subaccountId that is not one of your account's subaccounts now returns 404 SUBACCOUNT_NOT_FOUND and nothing is created; previously such a create could succeed with default settings. 400 and 403 refusals now include a code you can branch on (for example PROVIDER_NOT_ENABLED_FOR_ACCOUNT, PROVIDER_NOT_SUPPORTED_FOR_COUNTRY, INVALID_LINK_FILTERS, PLAID_EC_NOT_PROVISIONED) instead of matching on message; status codes and messages are unchanged. The create also accepts an optional language (a BCP 47 tag such as en or sv-SE) for the hosted screens. For now the screens stay in English unless Astrada has turned the language on, and the request still succeeds.

Unified Enrollment SDK v2

  • SDK v2 starts every session on the card number and picks the route for you. The user types the first 8 to 11 digits and presses Continue. The welcome screen, the chooser and the v1 bulk screens are gone, and the full card number is typed only on the card form, which opens with those digits filled in. On admin pages (persona: "admin"; persona has no default, and open() refuses a session without it), a card from a program Astrada has bulk-enrolled before opens a program screen leading to the bulk kickoff; a program that is likely bulk-capable gets an Ask Astrada to confirm callout alongside Enroll this card now; an Amex card goes to its bank link when bank linking serves Amex; other cards go to the bank link, the card form or "This card can't be enrolled here", as your settings allow. With persona: "cardholder" (employee pages) bulk is never shown. New events include route-decided, bin-disputed, company-connection-needed and bulk-confirmation-requested, and onSuccess carries next. A new optional locale option is accepted (English is the only language today). The kickoff sends a requestId, so a retried kickoff never creates a second request. Load v2 with https://sdk.astrada.co/unified/v2/unifiedEnrollmentSdk.js; never load v1 and v2 on the same page. Try it in sandbox first, from https://sdk.sandbox.astrada.co/unified/v2/; your SDK client needs the network-bulk-enrollments:write scope for the kickoff and the confirm request. Ask your Astrada contact for the v2 migration guide.

GET /webhooks

  • Listing webhooks filtered by subaccountId no longer times out on accounts with many webhooks. Unfiltered listing, ordering, limits and the cursor format are unchanged, and existing cursors keep working.

Sandbox

POST /simulate/ingestion/vcf

  • VCF simulation now finds your feed from the networkReference you created it with. A feed created with a zero-padded reference was stored without the leading zeros, so sending the original value returned 400 "No active feed". Both forms now resolve.