Enabled
statuscanManageAccountMembership
user rights can use the addDirectDebitFundingSource
mutation to create a Direct Debit funding source object. Please note that the external iban must belong to the Swan account holder owning the Swan account to be credited.Pending
to Enabled
. Depending on the type of funding source, the requirements vary:SepaDirectDebitCore
SepaDirectDebitB2B
Pending
or Enabled
status can be canceled by any account member with the canManageMemberships
user rights using the cancelFundingSource
mutation. The funding source is then moved to the Canceled
status and cannot be used anymore (a call to the initiateFundingRequest
mutation for example will return an error).initiateFundingRequest
mutation for example will return an error).AccountVerification
object.Enabled
status using a specific Swan account holder x external IBAN couple could for example be moved to the Canceled
status, but if a new funding source with the same couple is created, the AccountVerification
already is in the Verified
status (although a new payment mandate is generated).pendingVerification
to the Verified
statuspendingVerification
to the pendingReview
status. A verification from the Swan Compliance department is required to determine whether the concerned account verification must be moved to the Verified
or to the Rejected
status.AccountVerification
is moved to the Rejected
status by Swan when the owner of the external account is different from the Swan account holder owning the account the funding source is attached to.PaymentDirectDebitMandate
is a mandate where the Swan account holder (the debtor) gives Swan (the creditor) their authorization to pull money from an external account (an IBAN, a card). When the direct debit funding source scheme is SepaDirectDebit B2B, the mandate document provided by Swan must be transmitted to the bank owning the external IBAN that will be debited.FundingSource
creation as well as internal information (such as the Swan account holder name).CanManageMemberships
user rights on the concerned account, using the consentUrl provided as a return to the funding source creation mutation. it is then moved from the ConsentPending
status to the Enabled
status.FundingLimit
parameter is applied at account holder level. The funding limit can be defined as the maximum amount that can be credited onto a Swan account using a fundind source over a pre-defined number of calendar days. The amount and duration are defined per account holder by Swan, based on a global risk and fraud analysis.SepaDirectDebitCore
SepaDirectDebitB2B
Booked
status on the concerned Swan account, the reserved amount is added to the account reserved
balance and is deducted from the account available
balance, i.e. that it cannot be used until the rolling reserve duration is over. When the rolling reserve duration is over, the reserved balance is debited from the concerned amount and the available balance credited of the same amount, so that funds can be used.Enabled
status can be used with the initiateFundingRequest
mutation by any account member with the canInitiatePayments
user rights. This sensitive operation requires consent (Swan regular consent system) from the end-user. A payment (SepaDirectDebitCore for example if the Funding Source is using the Sepa Direct Debit Core scheme) is created in the Upcoming
status and is moved to the booked status max 2 inter-bank business days following the funding request initiation.requestedExecutionAt
parameter. Rejected
status when the requested amount exceeds the already used funding limit for the concerned funding source.SepaDirectDebitCore
SepaDirectDebitB2B