Steps

• Create a direct debit mandate object via the API or the dashboard (type = “bacs_debit”, direction = “outgoing”), related to the relevant connected account operated by your Bacs sponsor bank. Make sure that you configured your Bacs SUN with your Mambu Payments Account Manager.
• Mambu Payments will batch all Bacs direct debit mandates into AUDDIS files and will send them to Bacs. The Bacs 3 days processing cycle starts.
• During the 3 days lifecycle, Bacs can return Input reports and receiving banks can issue bank-returned AUDDIS reports, both able to reject and cancel such mandates. In both cases, Mambu Payments will take care of switching the corresponding direct debit mandate objects to rejected or canceled.
• On day 4, Mambu Payments will switch the remaining pending_review mandates to active.

Sequence diagram

sequenceDiagram
		participant C as Customer
    participant N as Mambu Payments
    participant S as Bacs
    autonumber

    C->>+N: POST /direct_debit_mandate
    N->>-C: 200
		N->>N: Batch AUDDIS file
		N->>S: Send AUDDIS file
		N-->>C: Event direct_debit_mandate:pending_review
		alt Technical error
			S->>N: Send Input Report
    N-->>C: Event direct_debit_mandate:rejected
			C->>C: Manual review
		else Functional error
			S->>N: Send bank-returned AUDDIS report
    N-->>C: Event direct_debit_mandate:canceled
			C->>C: Manual review
			
		end
		N->>N: Wait 4 business days
		N-->>C: Event direct_debit_mandate:active
		
		note over C: Mandate is active <br/> and can now be used