POST /transaction/check_authorization → endpoint removal
Paystack API
Stopped working
On March 1, 2023, the endpoint POST /transaction/check_authorization was deprecated and stopped working after Paystack sunsetted a legacy integration rail. Calls to POST /transaction/check_authorization fail after this date. This affects any integration relying on that endpoint to verify authorizations.
Calls it hits
POST /transaction/check_authorization
What to use instead of these calls
Charge the authorization directly with POST /transaction/charge_authorization, or use POST /transaction/partial_debit for a partial amount, and handle a failed charge. No endpoint replaces the pre-charge funds check, so the payment flow has to change.
No endpoint replaces the pre-charge funds check: the payment flow has to change.
In Paystack API's words
we sunsetted one of our legacy integration rails that has no support for 3DS 2.0. The check authorization endpoint is powered by this rail and as a result, we deprecated the endpoint.
Facts
- API
- Paystack API
api.paystack.co - Kind
- Endpoint removal
- Announced
- March 1, 2023
- Takes effect
- March 1, 2023
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Paystack API's own pages
Questions
When does this change take effect?
Calls to POST /transaction/check_authorization on Paystack API stopped working on March 1, 2023.
What happens to calls after March 1, 2023?
They have failed since March 1, 2023.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.