canManageMembers
right can give multiple users rights to that account and those rights translate to an account membership.)addCard
mutation. This mutation can only be called on behalf of an Account Member with the canManageAccountMembership
rights.accessToken
using the name of the account member. The new card is thus created with the ConsentPending
status and a consentUrl
is returned which invites the user to start Strong Customer Authentication with Swan. Learn More. Once the Strong Customer Authentication process is finished, the new card changes to Activated
status.cardContractExpiryDate
we will renew every three years until we hit this date.addCards
mutation. It works nearly the same way as addCard
with two additional features: physicalCard
field with the delivery addressspendingLimit
field is available directly, no need to update after creating the card.accessToken
using the name of this account member. The new cards are thus created with ConsentPending
status and a consentUrl
is returned which invites the user to start Strong Customer Authentication with Swan. Learn More. Once the Strong Customer Authentication process is finished, the new cards change to Processing
status.Enabled
status. Be aware that depending on how many cards you're creating, it can take up to several minutes to complete the process.addCardsWithGroupDelivery
mutation. It works just like addCards
, except all the cards will be sent together in one package. It's more cost-effective, and better for the planet!updateCard
mutation.cardContractExpiryDate
: null
if you don't want to set an expiration dateinternational
: allow payments outside of the account holder's countrywithdrawal
: allow or disable cash withdrawalsnonMainCurrencyTransactions
: allow or disable transactions outside of the card's currencyeCommerce
: allow or disable transactions at eCommerce sitesmonthlySpendingLimit
: fixed by the member within the limits set by Swaninternational
and nonMainCurrencyTransactions
is important. international
disabled, payments can only be made in the account holder's country, but you can still pay using other currencies (e.g. you are French and can pay in France using USD, but you can't make any payments outside of France).nonMainCurrencyTransactions
disabled, payments can be made in other countries but not using other currencies (e.g. you are Italian and can pay using Euros in other countries like Germany, but cannot use any currency other than the Euro).accessToken
using the name of the user behind the modification with the right canManageAccountMembership=true
on the linked account. Learn More.consent
resource containing the consentUrl
. The url allows you to redirect the user making the modification to Swan's strong authentication. Learn more.version
is increased by 1.eCommerce=false
allows the account member to temporarily block all e-commerce payments. The end client must then write to [email protected], after which Swan can renew the card number.cardUrl
available in the card
query is for a website that displays the card with its design and its sensitive hidden information. We suggest you integrate it into your product in an iframe or a webview. This url is available 1 hour after you query it, then renew the query to get another cardUrl.viewCardNumbers
mutation which returns a consent
. When you do this, make sure you are authentified with an accessToken
using the name of the card's account member. Then a consentUrl
is returned which invites the user to start the Strong Customer Authentication with Swan. Learn More.redirectUrl
set up during the viewCardNumbers
mutation.cancelCard
mutation. Each card associated to the virtual card will no longer be usable. The card's status will be Canceling
during the process and will change to Canceled
once it is done.cancelPhysicalCard
.Learn more.
To cancel only a digital card you must use cancelDigitalCard
.Learn more.addSingleUseVirtualCard
mutation.canManageAccountMembership
rights.accessToken
using the name of this account member. The new card is thus created with the ConsentPending
status and a consentUrl
is returned which invites the user to start the Strong Customer Authentication with Swan. Learn More. Once the Strong Customer Authentication process is finished, the new card changes to Enabled
status.printPhysicalCard
mutation which returns a consent
. When you do this, make sure you are authentified with an accessToken
belonging to a member with the canManageAccountMembership
access right on the account . Then a consentUrl
is returned which invites the user to start Strong Customer Authentication with Swan. Learn More.PhysicalCardToActivateStatus
object, with the estimated date of delivery in the estimatedDeliveryDate
field. The carrier and tracking number are available in the shippingProvider
and trackingNumber
as sos on as they're available. The card's status will be ToActivate
until the card is activated.activatePhysicalCard
mutation which returns a consent
. When you do this, make sure you are authentified with an accessToken
using the name of the card's account member. Then a consentUrl
is returned which invites the user to start the Strong Customer Authentication with Swan. Learn More.viewPhysicalCardPIN
mutation which returns a consent
. When you do this, make sure you are authentified with an accessToken
using the name of the card's account member. Then a consentUrl
is returned which invites the user to start the Strong Customer Authentication with Swan. Learn More.redirectUrl
chosen during the PhysicalCardPIN
mutation.isPINReady
boolean to the physical card'sstatusInfo, with
ToActivate
status. This is true
when the PIN is available.resumePhysicalCard
mutation which returns a consent
. When you do this, make sure you are authentified with an accessToken
using the name of the card's account member. Then a consentUrl
is returned which invites the user to start the Strong Customer Authentication with Swan. Learn More.suspendPhysicalCard
mutation.resumePhysicalCard
mutation which returns a consent
. When you do this, make sure you are authentified with an accessToken
using the name of the card's account member. Then a consentUrl
is returned which invites the user to start the Strong Customer Authentication with Swan. Learn More.Renewed
with the delivery details available in the PhysicalCardRenewedStatus
object, and its estimated date of delivery in the estimatedDeliveryDate
field. You'll find the carrier and tracking number in the fields shippingProvider
and trackingNumber
as soon as they're available.cancelPhysicalCard
mutation by selecting the reason for cancellation.printPhysicalCard
mutation again.addDigitalCard
mutation which returns a consent
. When you do this, make sure you are authentified with an accessToken
using the name of the card's account member. Then a consentUrl
is returned which invites the user to start the Strong Customer Authentication with Swan app. Learn More.cards
query.cancelDigitalCard
mutation.