RejectedReasonCodesfor card transactions have been added in order to provide you with a greater level of detail and an improved experience. These new values, listed as
COMING SOONare not populated but will be in the next Swan release, therefore please make sure to take these changes into account:
statusesfor a given Account Membership using the
paymentsquery in order to align with other queries.
initiateCreditTransfermutation has been updated to match current SEPA guidelines.
cardUrl(card query) is now updated when the Account Member name is updated
updateUserConsentSettingsmutation. Learn more
finalizeOnboardingmutations you are not obligated to use our #nocode interfaces. You can onboard customers directly from your product, if you prefer. Learn more
resourceId. View each webhook's KPIs for the last 7 days: hits, counter, and error rate. We also added 2 new events:
Upcomingcan now be canceled using the
accountsqueries has been fixed. It might break if you implement the filter on the front-end. These queries now only return the requested number of items, rather than all items at once.
addAccountMembershipsmutation. Learn more
addCardsmutation. Since card creation is executed asynchronously, we created a new card status:
Processing. We deprecated the
statusfilter on the
cardsquery and created
statusesso you can filter when there are multiple ones. Learn more
ibanValidationquery helps you verify the format of an external IBAN, get all available bank info (name, BIC code, etc.) and account data available for this IBAN, as well as the reachability of this IBAN across all SEPA schemes. Learn more
account.receivedDirectDebitMandatesquery and can be suspended with the
suspendReceivedDirectDebitMandatemutation or resumed with the
resumeReceivedDirectDebitMandatemutation. Learn more
addSingleUseVirtualCardconsent by using the new
viewCardNumbersproperty. This way, you save the time of one consent and can use the card immediately
generateAccountStatementmutation allows you to generate account statements on demand.
resumePhysicalCardmutations are now available.
transactionquery can now fetch its related
account. If you're using webhooks for transactions, this is very helpful.
categoryto: the card authorization event simulator, the payment control, the card transaction API
authorizationTypeto: the card authorization event simulator, the payment control, the card transaction API. Values include
namefield to the card in the API
shippingProviderwhen you order new physical cards
resourceIdin the consent callbacks Url
canManageMembershiprights to cancel a physical card
NotStartedas long as the legal representative is not idverified
scheduleStandingOrder: accept datetime format for
isPinReadywhen a physical card was printed before 5 PM Paris time
Developerrole for dashboard members. We encourage you to update members accordingly.
transactionby Id in the Graph
upcomingtransaction is executed, this same transaction is updated to Pending rather than being deleted. Learn more
cancelCardmutation Learn more
addSingleUseVirtualCardmutation. Learn more