Card
Swan lets you issue Mastercard debit cards to all Account members. (Remember: the account administrator with the canManageMembers right can give multiple users rights to that account and those rights translate to an account membership.)
No matter how many members are attached to an account, 1, or 50, or 500, you can issue a debit card to each member. Any payments made with a card will debit the account the member is linked to.
So basically, if you have an account with 50 members, and have issued a card to each member, all 50 cards would give access to the same pot of money.
Depending on the nature of an Account Holder, whether an individual or a company, the cards are considered Debit Consumer or Debit Business, respectively.
In this case, John & Kimberly are both members of the same account: MyLittleCompany's. They each have a card, and any money they spend with those cards will be withdrawn from MyLittleCompany's account.
In this case, Ursula has an individual account with just one member: herself.
While Swan offers a digital-first user experience, it's ultimately up to you what type of cards you'll issue: virtual, digital (Apple Pay or Google Pay), or physical.
Whenever you issue a new card, a virtual card number is instantly created that the Account member can already start using for e-commerce transactions. This new card can immediately go digital as well, through Apple Pay or Google Pay, letting account members easily start spending at physical sales points.
As for physical cards, Swan gives Account members the option to order a physical card. These are the good old plastic cards we are all familiar with. They can be used at sales points with any of the usual methods: swipe, chip + PIN code, or contactless.
In this case, Kafka Tamura received his virtual card instantly after ordering it. On day 2, he puts it in his smartphone and begins using it to pay for coffee and make payments at local businesses. On day 4, he puts it into his new smartwatch, too. On day 7, Kafka feels nostalgic for plastic cards and decides to order one of those.
Card design comes up several times during the account member's user experience. When ordering a physical card, and when consulting the web page that displays card numbers. If they're using Google Pay or ApplePay, it'll show up in their applications as well.
Swan proposes 2 standard card designs that have already been validated by Mastercard. You can personalize them with your brand and logo on the front side of the card. Just use our dashboard to upload your logo in SVG format. Once a standard card is ordered, the delivery delay is typically less than 7 days.
Black card personalizable with your logo in white monochrome
Silver card is more like a grey gradient with a matte finish, personalizable with your logo in black monochrome
Custom designs are possible too. Just send us a description of what you'd like: [email protected]
First, Mastercard will have to approve your design. After that, the delivery delay is about 8 weeks.
If you're not a developer, you can stop reading here. You'll be able to manage your cards with the web interfaces we provide you. If you're using the API, go ahead and keep reading.
You can add a new card to an existing Account member by calling the addCard mutation. This mutation can only be called on behalf of an Account Member with the canManageAccountMembership rights.
When you do this, make sure you are authentified with an 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 app. Learn More. Once the Strong Customer Authentication process is finished, the new card changes to Activated status.
If the account Member that made the request is the same as the cardholder, Swan will let you push the card into ApplePay or Google Pay if you so choose.
The card is automatically renewed unless if you transmit an end of contract date.
You can modify all card settings by calling the updateCard mutation.
cardContractExpiryDate:nullif you don't want to set an expiration dateinternational: permit payments outside of the countrywithdrawal: allow our 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 Swan
When you do this, make sure you are authentified with an accessToken using the name of the user behind the modification with the right canManageAccountMembership=true on the linked account. Learn More.
The request from this mutation returns a newly created consent resource containing the consentUrl. The url allows you to redirect the user making the modification to Swan app's strong authentication. Learn more.
Once the consent process is completed, the card is updated and its attribute version is increased by 1.
Card settings are valid for all payments linked to this card, whether they were made with a virtual, physical, or digital card.
At the slightest suspicion of fraud, 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.
The cardUrl available in the cardquery 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.
When the Account member wants to display sensitive information such as the card number, the CVC or the expiration date to make an eCommerce payment, you must call theviewCardNumbers 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.
Once the consent has been accepted, the card's sensitive information is displayed for 5 minutes. The client can then click the number to copy it to their clipboard. After they are done with the card info, they can click on the Ok button and be redirected to the redirectUrl set up during the viewCardNumbers mutation.
To immediately and permanently cease usage of a card and no longer be billed for it you must call the 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.
To cancel only the physical card you must use cancelPhysicalCard .Learn more.
To cancel only a digital card you must use cancelDigitalCard .Learn more.
You can add a new Single Use virtual card to an existing Account member by calling the addSingleUseVirtualCard mutation.
This type of card lets you avoid 3DS consent during e-commerce payments as well as payments limited to a single merchant. Recurring payments (music/video streaming, AdWords, car payments...) are possible if the card's spending limits allow them.
This mutation can be called on behalf of any Account Member with the canManageAccountMembership rights.
When you do this, make sure you are authentified with an 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 app. Learn More. Once the Strong Customer Authentication process is finished, the new card changes to Enabled status.
The Single Use Virtual Card is never renewed. It cannot be physically printed, nor used with Apple Pay and Google Pay.
To add Single Use Virtual Cards with a project access token, please contact us: [email protected]​
When an account member orders a card for the first time, you can get it printed for them by calling the 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 the Strong Customer Authentication with Swan app. Learn More.
At that point, the Account member chooses their physical card's 4 digit PIN code. If a PIN code has not been chosen, we will automatically generate one after 24 hours.
Once the PIN code is known in our system, the card will be delivered to the account member within 72 hours. The delivery details are available in the PhysicalCardToActivateStatus object, with the estimated date of delivery in the estimatedDeliveryDatefield. The carrier and tracking number are available in the fields shippingProvider and trackingNumber as soon as they're available. The card's status will be ToActivate until the card is activated.
By design, cards will be delivered in the letter below. If you prefer to use your own packaging please get in touch: [email protected]
You can activate our physical cards either by making a first payment with the PIN code or by calling the 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 app. Learn More.
You can display the physical card's PIN by calling the viewPhysicalCardPINmutation 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.
Once the consent has been accepted, the PIN code is displayed for 5 minutes. After getting the PIN code, the user can click on the Ok button and he is redirected to the redirectUrl chosen during the PhysicalCardPIN mutation.
If your card was created before 5:00 p.m. you can call the mutation starting from 5:30 p.m. that same day. Otherwise, you'll have to wait until the next day 5:30 p.m. to start calling the mutation. To help you out we have added the isPINReady boolean to the physical card'sstatusInfo, with ToActivate status. This is true when the PIN is available.
​
If the account Member makes 3 incorrect PIN attempts, the physical card is suspended and no further payments can be made, neither online (e-commerce) nor at a physical sales point. Only payments through Apple Pay or Google Pay will continue to work.
To unblock a physical card you must use the resumePhysicalCardmutation 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.
You'll then have to wait 24 hours before the physical card can be used again.
You can temporarily block a physical card with the suspendPhysicalCardmutation.
To unblock a physical card you must use the resumePhysicalCardmutation 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 are renewed automatically. About 1.5 months before the expiration date, the status of the physical card changes to 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.
When a physical card is renewed, the card numbers change but the 4 digit PIN code remains the same to simplify the UX.
When a card has been undelivered, lost, stolen or damaged, you must call the cancelPhysicalCardmutation by selecting the reason for cancellation.
Be careful, if the physical card has been lost or stolen, and if the client has already added the card to Apple Pay or Google Pay, don't forget to ask your client if their smartphone has been lost or stolen so that you can also delete these digital cards. Otherwise, the digital cards will continue to work. For some clients, this could be useful, if they still have their smartphone and wish to make payments while waiting for their new card to be delivered.
If you wish to send a new card to your client, just call the printPhysicalCard mutation again.
We support Apple Pay and soon Google Pay.
There are 2 ways to provision digital cards in Apple Pay or Google Pay:
Push from Swan App: by calling the
addDigitalCardmutation which returns aconsent. When you do this, make sure you are authentified with anaccessTokenusing the name of the card's account member. Then aconsentUrlis returned which invites the user to start the Strong Customer Authentication with Swan app. Learn More.Then the Swan app proposes adding the card to Apple Pay or Google Pay depending on the brand of the account member's smartphone.
Enter card numbers directly into Apple Pay or Google Pay: a client can go digital by entering their card number directly into Apple Pay or Google Pay.
The list of digital cards is available in the cards query.
Swan takes care of updating digital cards with Apple Pay and Google Pay. It's a clear advantage, as this requires no action from you nor your client.
When you wish to instantly and permanently delete an Apple Pay or Google Pay digital card, you must use the cancelDigitalCard mutation.
