Improvementsโ
๐ค In order to reduce user binding errors when adding account memberships, we now consider the account member's birthLastName
. If it matches their lastName
, we won't raise a lastNameMatchError
.
๐งญ Enriched transaction information is now available for all card transactions, including those from the start of Swan. When available, detailed merchant and transaction data can be accessed through the API, Dashboard, and Web Banking.
๐ Get information about supporting documents related to onboarding and account holder verification from your Dashboard. We also revamped the document collection portal.
๐ฏ Access and change the Sandbox user you're impersonating when using Web Banking in the Sandbox environment.
Breaking changesโ
๐ณ As announced on August 1st, we now use additional issued card rejection reason codes: CanceledByCardHolder
, DigitalCardDeactivated
, DigitalCardEnrollmentInvalid
, DigitalCardRefusal
, DigitalCardSuspended
, DigitalCardTokenInvalid
, InPersonTransactionsNotAuthorized
, MagstripeNotSupported
, MerchantNotFound
, PeriodTransactionNumberLimitExceeded
, PinRequired
, and ThreeDsError
.
Upcoming breaking changesโ
๐ข In 4 weeks, we're introducing a webhook subscription limit. In order to avoid overconsumption caused by too many subscriptions to the same event, you'll be restricted to 10 subscriptions per Sandbox event and 5 subscriptions per Live event.
โ ๏ธ In 4 weeks, we're adding a new value to the SupportingDocumentPurpose
Enum: PepDeclaration
.
โ In 8 weeks, if you call the API with a user access token attributed to a Blocked
user, it will be rejected.