Statuses and lifecycle

The lifecycle of an account membership, from ConsentPending through to Disabled, and the lifecycle of an account administrator change request.

Statuses

Account membership status	Explanation
ConsentPending	An account membership request was sent using the addAccountMembership mutation and is waiting for the inviter's consent. Memberships with the status ConsentPending can't be updated. If there's an error in the invited account member's information, cancel the invitation and add a new account membership with the addAccountMembership mutation. Next steps: If the inviter consents, the status moves to InvitationSent. The account membership status moves to Disabled if the inviter opens the consent flow but doesn't consent, or if the consent request expires before the inviter consents. For Disabled memberships because of expired consent, querying AccountMembershipDisabledStatusInfo shows the reason as InvitationExpired. Subscribe to the AccountMembership.Disabled webhook to get notified when a membership moves to Disabled.
InvitationSent	An invitation was sent to the invited account member. Next steps: If the invited account member accepts the invitation and provides personal information that matches the information Swan already has about them, the status moves to Enabled. If the invited account member accepts the invitation, but provides personal information that doesn't match the information Swan already has about them, the status moves to BindingUserError. If the invited account member declines the membership, the status moves to Disabled.
Enabled	All user information matches, the account member has been awarded the correct identification level, and the account member can use their account membership and corresponding permissions. Next steps: The membership can be Suspended (temporarily) or Disabled (permanently).
BindingUserError	The personal information you submitted about the invited account member doesn't match the information they provide during the sign-up process. The mismatch must be solved before continuing. Next steps: When the mismatch is solved, the status moves to Enabled. The membership can also be Disabled.
Suspended	Account membership is suspended and not available for use. Account memberships can be suspended for various reasons, including a request from you or the account's legal representative, or a Swan action in the case of suspicious activity. Next steps: Restore the account membership's previous status with the API. Cancel the account membership with the API.
Disabled	Account membership is disabled, is no longer available for use, and can't be restored. When an account member's membership is disabled, their recurring single-use virtual cards are automatically reassigned to the account's legal representative. Subscribe to the AccountMembership.Disabled webhook to get notified when a membership moves to Disabled.

For the sequence of API calls that adds a membership and binds the invitee to it, review the invitation sequence diagram.

Binding user errors

The account membership status can be BindingUserError for several reasons, including the following scenarios:

• The information you submitted about the invited account member doesn't match the information they provided when signing up for an account.
• The user hasn't completed identification.
• If you invited the account member by verified email, the email you provided might not match the email they used to sign up, or they might not have verified their email yet.

Account members whose membership status is BindingUserError can still access basic account and card information, but they can't perform any sensitive operations, such as making a transfer or viewing their card numbers.

At least one of the following booleans must be true for an account membership to have a user binding error:

Error	If true	Update
firstNameMatchError	There's a mismatch with the first or given name.	Update restrictedTo > firstName.
lastNameMatchError	There's a mismatch with the last name or birth last name.	Update restrictedTo > lastName.
birthDateMatchError	There's a mismatch with the birth date.	Update restrictedTo > birthDate.
phoneNumberMatchError	There's a mismatch with the phone number.	Update restrictedTo > phoneNumber.
emailVerifiedMatchError	There's a mismatch with the email, or the user didn't verify their email.	Update email, or send user new authorization URL to verify email.
idVerifiedMatchError	The user wasn't assigned the right identification level.	The user needs to complete another identification process.

To fix binding errors, follow the guide to fix a user binding error for the mutation walkthrough.

Updating account members

After an account member's status is Enabled, updating their personal details doesn't cause a user binding error. If fraud is suspected, suspend the membership.

Closing or closed accounts affect memberships: management and payments stop at Closing, and memberships are Disabled one year after Closed.

Account administrator change statuses

An account administrator change request has its own lifecycle, separate from the membership statuses above.

Status	Explanation
Ongoing	The change request was created. The requester must submit the form within 7 calendar days.
Pending	Swan's KYC team is reviewing the submitted form. No action is required from the requester.
WaitingForInformation	Swan's KYC team requested additional information or documents. Swan shares a new supporting document collection URL with you to forward to the requester. The original form URL can no longer be used at this stage.
InvitationSent	Swan's KYC team invited the new administrator to the accounts. The new administrator must accept the invitation and verify their identity. This status is skipped if the new administrator already has access to the accounts.
Expired	Final. The form wasn't submitted within 7 calendar days. The requester needs to start a new request.
Verified	Final. Swan set the new administrator as the legal representative on all accounts.
Refused	Final. The KYC team refused the request. No changes were made.

warning

When a change request expires, all form data becomes inaccessible. Swan doesn't retain the personal information entered on the expired form.