Configure consent notifications

You can declare a preferred notification channel for your users and configure how your consent notifications appear.

If you're using Swan's Web Banking interface, Swan sends a text message to your users for one-time passwords, logins, and consents, regardless of preferred channel and configuration.

Timeout

Your integration has two seconds to respond to a consent notification. If your response is anything other than a 200 OK HTTP, or there's no response at all, Swan redirects the user to the standard text message consent flow. This timeout complies with 3-D Secure (3DS) requirements.

When to use consent notifications

Consent notifications are relevant when you have both desktop and mobile apps, or when you want to optimize 3-D Secure (3DS) on mobile.

Consent flows only

Consent notifications are only available for Consent flows (sensitive operations). They can't be used for OAuth flows such as login or authentication.

How consent notifications work

By default, when a user performs a sensitive operation on desktop and needs to consent, Swan sends an SMS to their smartphone with the consent link.

With consent notifications configured, when a user performs a sensitive operation on desktop, your mobile app receives a notification so the user can consent inside your mobile app. This redirects desktop users to your mobile app to give consent.

Think of consent notifications as another way to give consent alongside SMS and QR codes. This is similar to how some purchases on desktop sometimes require approval from your banking app: you initiate an action on desktop and approve it on your mobile app.

Declare preferred notification channel

You can specify how your user would like to receive consent notifications, referred to as their preferred channel.

Call the updateUserConsentSettings mutation with a project access token.
Enter the user's userId.
Choose the preferred channel:
1. Sms (default value): Swan sends a text message to the user with the SCA link to open on their mobile device.
2. App: You receive a notification, then send the SCA link to your user yourself.

Mutation

Open in API Explorer

mutation PreferredChannel {
  updateUserConsentSettings(
    input: {
      userId: "$YOUR_USER_ID"
      preferredNotificationChannel: Sms
    }
  ) {
    ... on UpdateUserConsentSettingsSuccessPayload {
      __typename
      userConsentSettings {
        preferredNotificationChannel
      }
    }
    ... on UpdateUserConsentSettingsTokenRejection {
      __typename
      message
    }
  }
}

Payload

Notice the preferred channel Sms (line 6).

{
  "data": {
    "updateUserConsentSettings": {
      "__typename": "UpdateUserConsentSettingsSuccessPayload",
      "userConsentSettings": {
        "preferredNotificationChannel": "Sms"
      }
    }
  }
}