Direct Debit Integration Guide: Mandate Setup

• It's important to note that the account the E-mandate is being set up on MUST be used for the ₦50 funding. This funding acts as the customer's approval of the mandate. If the user fails to send the ₦50 the mandate will be inactive and unapproved
• Your customer can choose either Fidelity or Paystack-Titan accounts as the authorization transfer accounts when creating Direct Debit e-mandates. This bank accounts are returned in the transfer_destinations field under the data objects.
• Note that the ₦50 transfer must come from the bank account that requires mandate setup.
• The user must send the ₦50 money within 6 hours, else the mandate will be cancelled and they have to create another mandate again.
• When such mandate is cancelled, the mandate cancelled event (events.mandate.action.cancel) is sent with the reason for cancellation included in the response.

Please be aware that after sending an NGN 50 amount to a NIBSS-provided account, the mandated account will enter a ready-to-debit status in under 1 hour for an E-Mandate. This means your transactions will be processed more quickly, significantly reducing waiting times. A ready-to-debit webhook event will be sent to confirm when the account is ready for debiting.

For instance, if a mandate is created and approved at 4:00 PM, it will now be ready for debiting by 5:00 PM.

• variable: When debit type is variable the amount is the total debit/money a business plans to retrieve from a customer over the set period. Debits can be varied

• fixed: When debit type is fixed the amount is that which the business wants to retrieve per debit and then the total debit is automatically calculated based on that amount. Note that once the fixed amount is set on mandate authorisation, it is immutable.