Deactivate a Recipient
Authentication
Path parameters
The unique identifier of the Recipient or legacy Bank Account (the legacy BankAccountId value can be used on this endpoint).
Request
Allowed values: DEACTIVATED
The status of the recipient:
DEACTIVATED– Value to send to permanently disable the recipient so it can no longer be used. The Recipient must beACTIVEto be deactivated.
Response
Max length: 128 characters (see data formats for details)
The unique identifier of the object.
Returned values: PENDING, CANCELED, ACTIVE, DEACTIVATED
The status of the recipient:
PENDING– ForPAYOUTscope recipients, the user must complete SCA before the recipient can becomeACTIVE. ForPAYINscope recipients, the recipient creation is in progress.CANCELED– SCA was not successfully completed and the recipient creation request was canceled. To retry, create another recipient to retrieve anotherPendingUserAction.RedirectUrl. TheCANCELEDstatus does not apply ifRecipientScopeisPAYIN.ACTIVE– Recipient creation was successful (including SCA ifRecipientScopeisPAYOUT) and the recipient is ready to be used for payouts.DEACTIVATED– The recipient has been permanently deactivated and can no longer be used.
Unix timestamp (UTC) of the date and time the object was created.
Length: 1–50; cannot contain: &,'/ (pattern:^(?!.*[&,'/]).{1,50}\$)
A user-friendly name to identify the account. This value cannot be changed once the recipient is created.
Returned values: InternationalBankTransfer, LocalBankTransfer
The payout method of the recipient:
LocalBankTransfer– The account can only receive the corresponding localCurrencyfor theCountryvia the domestic payment rail (e.g.EURvia a SEPA local scheme to a SEPA country,GBPvia FPS to aGBaccount,USDvia ACH to aUSaccount, etc). Payouts in non-local currencies return an error.InternationalBankTransfer– The account can receive both non-local currencies via SWIFT and also local currency via domestic rails.
Returned values: Individual, Business
The recipient type:
Individual– An account held by a natural person, requiring theIndividualRecipientproperty.Business– An account held by a legal entity, requiring theBusinessRecipientproperty.
Possible values: AED, AUD, CAD, CHF, CNH, CZK, DKK, EUR, GBP, HKD, HUF, ILS, JPY, MXN, NOK, NZD, PLN, RON, SAR, SEK, SGD, TRY, USD, ZAR
The currency of the recipient.
Format: Two-letter country code (ISO 3166-1 alpha-2 format)
The destination country of the payout method.
Returned values: PAYIN, PAYOUT
The scope of the recipient:
PAYOUT– Usable for payouts and in pay-in use cases. APAYOUTrecipient can only be created by a user with theUserCategoryOWNERand requires SCA.PAYIN- Not usable for payouts but only usable for pay-in use cases, such as direct debit and refunds using payouts. APAYINrecipient can be created by a user with theUserCategoryPAYERorOWNER, and does not require SCA.
Both PAYIN and PAYOUT scopes can be created for either InternationalBankTransfer or LocalBankTransfer, and for either IndividualRecipient or BusinessRecipient, and for any Currency.
Max. length: 255 (pattern: ^.{0,255}\$)
Custom data that you can add to this object. This value cannot be changed once the recipient is created.
Returned values: USER_PRESENT, USER_NOT_PRESENT
The SCA context provided in the create request. Returned in the create response and when viewing the recipient if a ScaContext value was sent when the recipient was registered. Omitted otherwise.
The account holder if the RecipientType is Individual.
The account holder if the RecipientType is Business.
The account details if PayoutMethodType is InternationalBankTransfer.
The account details if PayoutMethodType is LocalBankTransfer, depending on the Currency. One of:
Object containing the RedirectUrl needed for SCA redirection if triggered by the API call (otherwise returned null).