API Changelog
Stay up-to-date with the latest changes on our APIs
Upcoming changes
We are working on exciting features. While we work, keep building!
December 2021
We updated the statuses of refunds to better capture the state of a refund:
pending
: The refund initiated, waiting for response from the processor.processing
: The refund has been received by the processor.processed
: The refund has successfully been processed by the processor.failed
: The refund cannot be processed. Your account is credited with refund amount.
When a refund is initiated for a transaction, the transaction's status previously showed reversed
regardless of whether the refund had been processed. We're now better reflecting the status of a transaction with the following:
reversal pending
: The refund is pending or still processing.reversed
: The refund has been successfully processed.success
: The refund failed and your account is credited with the refund amount.
We now send webhook events to monitor the state of a refund:
- refund.pending
- refund.processing
- refund.processed
- refund.failed
November 2021
We added three new statuses to the SubscriptionAPI:
non-renewing
: The subscription is still active but won't be charged on the next payment date and will be marked as completed.attention
: The subscription is still active, but there was an issue while trying to charge the customer's card. The issue can be an expired card, insufficient funds, etc. We'll attempt charging the card again on the next payment date.cancelled
: The subscription has been cancelled.
October 2021
- We deprecated support for BVN type on the Customer ValidationAPI. Going forward, we advise against using the
type: "bvn"
andvalue
parameter in the request body in favour of Bank Account validation for existing and new customers.
September 2021
- We added
account_number
to the request body of the Customer ValidationAPI. This will require merchants to make use of Bank Account validation for existing and new customers.