Square API
offline_payment_details body parameter removal on POST /v2/payments
Stopped workingSubscribe to Square APIShare
Calls to POST /v2/payments, body parameter offline_payment_details on Square API stopped working on November 19, 2025.
Calls it hits
POST /v2/paymentsbody parameter offline_payment_details
What to use instead of these calls
Stop sending offline_payment_details in CreatePayment requests.
In Square API's words
The offline_payment_details property of the CreatePayment request is DEPRECATED. It will be retired in 90 days on November 19, 2025
Facts
- API
- Square API
connect.squareup.com - Kind
- Parameter removal
- Announced
- August 20, 2025
- Takes effect
- November 19, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Square API's own pages
Questions
When does this change take effect?
Calls to POST /v2/payments, body parameter offline_payment_details on Square API stopped working on November 19, 2025.
What happens to calls after November 19, 2025?
They have failed since November 19, 2025.
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.
More from Square API 5
-
POST /mobile/authorization-codeEndpoint removal Stopped working -
POST /v2/locations/{id}/transactions*Endpoint removal Stopped working -
No date
/v2/customers/{id}/cards*Endpoint removal Deprecated, no date -
No date
/v2/labor/shifts*Endpoint removal Deprecated, no date -
No date
GET /v2/locations/{id}/transactions*Endpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.