Skip to main content

SlimPay Help Center

Direct debit reimbursements



Depending on your business needs, you may want to return funds to your customer. For that you need to reimburse the payment. Our solution allows you to reimburse a payment via API or via Dashboard. You can reimburse a customer partially or in full. 

Refer to this page for a more technical explanation on how to execute reimbursements via our API or Dashboard. 

In case of a direct debit, we advise you to wait 5 working days after the execution date before reimbursing. This delay takes into account the potential for payment incidents (see the article on R-Transactions). Without this waiting period, you may reimburse a transaction that could be rejected. 

For all cases, before issuing a reimbursement, bear this in mind: 

  • Your customer must have an active mandate.
  • The refund amount must be less than or equal to the total amount debited from the customer's account in the past 14 months.
  • The refund amount must be less than or equal to your available funds.
  • Your reserve cannot be used to make reimbursements. It is only used to cover R-transactions. 

Partial reimbursements

It is also possible to partially reimburse a payment. In case of a partial reimbursement, you only return a part of the charged amount to your client.

In the event you have multiple direct debits executed on a mandate, you can reimburse the total amount collected via that mandate during the last 14 months, in a single request. Thus, you can eventually reimburse more than the amount of the initial direct debit payments.


Cancel a reimbursement

It is not possible to cancel a reimbursement, the payment is directly sent to the bank for processing.


Status management

When a reimbursement is initiated, the reimbursed (original) payment will not be affected, and will stay in the processed status. A reimbursement object is created with an initial toprocess status. After settlement, the reimbursement will move to the processed status.


Was this article helpful?
0 out of 0 found this helpful
Return to top