2023-Jan-12 Release Additions and Fixes
The following is the first in an ongoing series of API change logs, to be published with relevant releases to communicate additions and fixes to our APIs.
Enhanced Returns - API subscriptions with enabled wire services now can use PATCH payment with action “return” in the following new scenarios:
- Inbound complete payments where Source = Swift
- Inbound complete payments where Source = Book (i.e. Silvergate to Silvergate) and Currency Pair = EUR|EUR
As detailed in a separate blog we added scenarios where the rejection_reason field in the GET payment response is used to include known and available reasons why a payment is returned from a counterparty.
A fix was applied to an edge case bug that upon PATCH “return” the endpoint responded with “Error code: 40065.” Such payments should now be returnable via API as expected.
Additional bug fixes have been applied to POST payment and GET payment behavior, designed to reduce intermittent incidents of unfriendly fail messages.
- For GET, a 400 error with response “payment engine” should now receive an accurate 503.
- For POST, a 400 error with response “response ended prematurely” should now receive an accurate 503, and any idempotency key used is retriable.