Doc 1457/add example mutation for activatephysicalcard to the doc#521
Open
Doc 1457/add example mutation for activatephysicalcard to the doc#521
Conversation
✅ Deploy Preview for incomparable-tiramisu-91a96a ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
racene-swan
requested changes
Feb 6, 2026
Contributor
racene-swan
left a comment
racene-swan
left a comment
There was a problem hiding this comment.
Hey, some of the paragraphs are quite dense, which raises the reading grade. Try making it more active, and this should bring it down.
| Then a `consentUrl` is returned which invites the user to start Strong Customer Authentication with Swan. No newline at end of file | ||
| Physical cards can be activated in two ways: | ||
|
|
||
| 1. **First transaction**: The cardholder enters their PIN during an in-person Chip and PIN payment. |
Contributor
There was a problem hiding this comment.
Suggested change
| 1. **First transaction**: The cardholder enters their PIN during an in-person Chip and PIN payment. | |
| 1. **First transaction**: The cardholder enters their PIN during an in-person chip and PIN payment. |
|
|
||
| ## Activation reminder notifications {#activation-reminders} | ||
|
|
||
| To encourage timely card activation, Swan can send reminder email notifications to users who haven't activated their physical cards after the estimated delivery date. |
Contributor
There was a problem hiding this comment.
Can we simplify - it's currently sitting at a grade 14 for readability.
Contributor
There was a problem hiding this comment.
Making it more active will reduce the readability
| ### Payload {#payload} | ||
|
|
||
| The cardholder must consent to activate the physical card. | ||
| Open the `consentUrl` returned in the payload to complete Strong Customer Authentication with Swan. |
Contributor
There was a problem hiding this comment.
Suggested change
| Open the `consentUrl` returned in the payload to complete Strong Customer Authentication with Swan. | |
| Open the `consentUrl` returned in the payload to complete Strong Customer Authentication (SCA) with Swan. |
| The following tables list information about the available text message and email notifications. | ||
| Take note of the [account membership permissions](../accounts/memberships/index.mdx#permissions) required to receive each notification. | ||
| Account members won't receive the notification if they don't have the required permission. | ||
| You can query your project's notification reminder planning settings (timing intervals for reminder notifications) using the `notificationReminderPlannings` query. |
Contributor
There was a problem hiding this comment.
Can we simplify?
Use the notificationReminderPlannings query to check your project's reminder schedule.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.