Trustly Subscribe

Based on a direct debit mandate registered with BACS in the UK, Trustly only acts as a technical provider in setting up, sending, and storing mandates and transactions. Date, amount, and frequency of the payment are set up based on mandate registration. A mandate takes 5 days to confirm, thereafter payments are possible.

Requirements to enter TDD flow

Establish Data Mandatory Fields

  1. The user must be in the UK (GB, GG, JE, GI) as the current flow type.
  2. Pass the required data during the EstablishRequest within the establishData object.
  3. Email and address are mandatory, even though the API will not verify. If both are not entered, the user will have to manually type it in at Checkout.
  4. In compliance with GDPR, do not send the telephone number.
  5. Merchant reference is mandatory and unique per mandate.
  6. Merchant references must match the BACS requirement. Minimum requirements include:
    • A core reference may be up to 13 characters long and must be a minimum of 6 characters
    • Although any of the allowed BACS characters may be included in the core reference*, only upper
      case alpha and numeric characters will be considered in checking for the minimum length of 6
      characters. Use of “DDIC” in the first four characters of the reference is prohibited. This is
      reserved for PSP use only if:
    • It must not consist of all the same characters (e.g. all zeros)
    • It must be left-justified within field 10 of the DDI and Direct Debit record. This requires the first
      alpha/numeric character of the reference to appear in character position one of this field
    • It must be lodged with the paying PSPs exactly as it appears on a signed DDI
    • It must be unique for the sort code, account number, and SUN to ensure that the paying PSPs can
      accurately match Direct Debits to DDIs. It must not be possible to match the core reference quoted
      in the DDI wholly or in part to the core reference of any other DDI already held by the paying PSP
      for the same sort code, account number and SUN.
    • Valid characters are a space, A-Z, 0-9, -, &, and (.) Other allowed characters are space, ampersand (&), hyphen, full stop, and solidus (/).

Establish recurring transaction object

  1. Mandate must be confirmed (which takes 5 days), so the first start date of the recurring payments cannot be before that, else it will fail.
  2. AutomaticCapture must be true.

📘

Info

For more information, see Recurring Payments.

Other Transactions That Can Be Used

List transactions
Get Payments
Get User
Get Customer Data
Cancel Transaction

📘

Info

Cancel recurring transactions are possible on the current day before cut-off 8.30 pm (UK time)

📘

Info

Refund transactions are not possible on direct debit transactions

📘

Info

Event notifications should be enabled to retrieve status updates on the mandates and transactions

Expected Responses

TypeReasonDescription
ARUCS0Invalid details
ARUCS2Beneficiary deceased
ARUCS3I Account transferred
ARUCS5I No account
ARUCSBAccount closed
ARUCSCRequested by remitter
AWACS0Invalid details
AWACS3Account transferred
ARUDD0Refer to payer (basically means out of funds)
ARUDD2Payer deceased
ARUDD3Account transferred
ARUDD4Advance notice disputed
ARUDD5No account (or wrong account type)
ARUDD6No instruction
ARUDD7Amount differs (disputed amount)
ARUDD8Amount not yet due (in case payment is sent before DDI confirmed)
ARUDD9Presentation is overdue
ARUDDAService User differs (Details dont match DDI)
ARUDDBAccount closed
ADDACS0Instruction canceled refer to Payer
ADDACS1Instruction canceled by Payer
ADDACS2Payer Deceased
ADDACS3Account transferred to new bank
ADDACSBAccount closed
ADDACSCAccount transferred to new branch
ADDACSDAdvance notice disputed
ADDACSEInstruction amended
ADDACSRInstruction re-instated
AUDDIS1Instruction Canceled by Payer
AUDDIS2Payer deceased
AUDDIS3Account transferred
AUDDIS5No Account
AUDDIS6No instruction
AUDDISCDDI amount not zero
AUDDISFInvalid account type
AUDDISGPSP will not accept DD on account
AUDDISHInstruction expired
AUDDISIPayer Reference not unique
AUDDISKInstruction cancelled by paying PSP
AUDDISLIncorrect payers account details
AUDDISMTrx code/user status incompatible
AUDDISNTrx not allowed at payers branch
AUDDISOinvalid reference
AUDDISPPayer's name not present
AUDDISQService users name blank
DDIC1Amount differs
DDIC2No advance notice received by payer
DDIC3DDI cancelled by bank
DDIC4Payer has cancelled DDI with Service User
DDIC5No intruction held
DDIC6Signature fraudulent
DDIC7Claim raised at Service User Request
DDIC8Service user name disputed, payer does not recognise

Did this page help you?