This document describes the five (5) different scenarios for fee bearer on the new e-BillsPay middleware payment integration.
One of these scenarios MUST play out in every e-BillsPay payment request.
The values of the "feeBearer” and "DebitPeriodType" will always be provided in the payload of the payment request from e-BillsPay.
Scenario one
"feeBearer": "Customer",
"DebitPeriodType": "WeeklyDebit"
Expectation: Debit the payer the Amount and Fee, and then credit the beneficiary (Biller) the Amount less the fee.
Scenario Two
"feeBearer": "Customer",
"DebitPeriodType": "Standard"
Expectation: Debit the payer the Amount and Fee, and then credit the beneficiary (Biller) the Amount less the fee.
Scenario Three
"feeBearer": "Biller",
"DebitPeriodType": "Standard"
Expectation: Debit the payer the Amount only, and then credit the beneficiary (Biller) the Amount less the fee.
Scenario Four
feeBearer": "Biller",
"DebitPeriodType": "WeeklyDebit"
Expectation: Debit the payer Amount only and then credit the beneficiary (Biller) Amount less the fee.
Scenario Five
"feeBearer": "Biller",
"DebitPeriodType": " MonthlyDebit"
Expectation: Debit the payer Amount only and then credit the beneficiary (Biller) the same Amount
For the e-BillsPay accounting entries, please refer to this document e-BillsPay accounting/settlement entries
For further clarification and enquiries, please contact weboperations@nibss-plc.com.ng
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article