Skip to main content

Audience:

Developers

Sensitive operations

Sensitive operations are mutations that typically require your user's consent before execution. Some may not, depending on context (for example, suspendAccountMembership).

All links lead to the mutation's API Reference page. The Server-to-server column indicates whether the mutation is eligible for server-to-server consent: eligible () or not eligible ().

Accounts and onboarding

MutationServer-to-server
closeAccount
openAccount
finalizeAccountHolderOnboarding
finalizeOnboarding (deprecated)
updateAccountSettings

Account memberships

MutationServer-to-server
addAccountMembership
addAccountMemberships
suspendAccountMembership
resumeAccountMembership
updateAccountMembership

Cards

Adding cards

MutationServer-to-server
addCard
addCards
addCardsWithGroupDelivery
addDigitalCard
addDigitalCards
addSingleUseVirtualCard
addSingleUseVirtualCards

Virtual cards

MutationServer-to-server
updateCard
viewCardNumbers

Physical cards

MutationServer-to-server
printPhysicalCard
activatePhysicalCard
resumePhysicalCard
viewPhysicalCardNumbers
viewPhysicalCardPin

Funding

MutationServer-to-server
addDirectDebitFundingSource
initiateFundingRequest

Payments and transactions

Credit transfers

MutationServer-to-server
initiateCreditTransfers
initiateInternationalCreditTransfer
scheduleStandingOrder

Direct debit payment mandates

MutationServer-to-server
addReceivedInternalDirectDebitB2bMandate
addReceivedSepaDirectDebitB2bMandate
enableReceivedDirectDebitMandate
updateReceivedSepaDirectDebitB2bMandate

Other

MutationServer-to-server
refund

Trusted beneficiaries

MutationServer-to-server
addTrustedInternationalBeneficiary
addTrustedSepaBeneficiaries
addTrustedSepaBeneficiary