Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.

Skip to main content

View sensitive information

Prepare to view sensitive information​

The cardUrl available in the card query leads to a website that displays the card with its design and its sensitive hidden information.

Consider integrating it into your product with an iframe or a webview. This URL is available for one hour after you query it. After one hour, renew the query to get another cardUrl.

Information not visible

If information fails to become visible despite having the appropriate permissions, it may remain hidden due to regulatory restrictions based on your location.

View virtual card numbers​

To make online payments you usually need to provide the card numbers, the expiration date, and the CVC. All of this data is considered sensitive and is not directly available through the Web Banking interface or the API.

  1. When the Account member wants to display sensitive information, you must call the viewCardNumbers mutation which returns a consent.
  2. Replace $YOUR_CARD_ID with your card ID, and $YOUR_REDIRECT_URL with the URL you want to redirect the user to after viewing the card numbers.
  3. Make sure you are authenticated with a user access token using the name of the card's account member.
  4. Then a consentUrl is returned which invites the user to start the Strong Customer Authentication with Swan. You need to open a native pop-up to display the consentUrl. This URL will redirect the user to a page with the card numbers displayed with the card design.

Mutation​

Open in API Explorer
mutation ViewSensitiveInfo {
viewCardNumbers(
input: {
cardId: "$YOUR_CARD_ID"
consentRedirectUrl: "$YOUR_REDIRECT_URL"
}
) {
... on ViewCardNumbersSuccessPayload {
__typename
consent {
consentUrl
id
}
}
}
}

Payload​

{
"data": {
"viewCardNumbers": {
"__typename": "ViewCardNumbersSuccessPayload",
"consent": {
"consentUrl": "$YOUR_CONSENT_URL",
"id": "$YOUR_CONSENT_ID"
}
}
}
}

After the consent is accepted, the card's sensitive information is displayed for five minutes. The link to view the information is also valid for five minutes; the user can close and reopen the link anytime within those five minutes.

The user can click to copy any of the sensitive information to their clipboard. After they're done with the card info, they can click okay to be redirected to the redirectUrl set up during the viewCardNumbers mutation.

Swan card with information masked and revealed