API updates
We’ve released several enhancements and bug fixes to our API. Here are the highlights:
Pay In
-
Added the ability to skip a subscription payment by setting
totalAmount
to zero. See Pause a subscription or skip a payment for more details. -
Added the
expectedProcessingDateTime
field to the responses for these endpoints:- GET /MoneyIn/refund/{transId}/{amount}
- GET /MoneyIn/reverse/{transId}/{amount}
- POST /MoneyIn/refund/{transId}
When a paypoint has Enhanced Refund Flow enabled, the
expectedProcessingDateTime
field shows the date and time that a queued refund is expected to be processed.
Pay Out
Added the parentOrgId
filter with (eq, neq, in, nin)
operators to these endpoints:
- Query/batchesOut/{entry}
- Query/batchesOut/org/{orgId}
- Query/payouts/{entry}/{orgId}
- Query/payouts/org/{orgId}
- Query/bills/{entry}
- Query/bills/{entry}/org/{orgId}
- Query/vendors/{entry}
- Query/vendors/org/{orgId}
Pay Ops
- All instances of EIN values returned in API responses are now masked.
- Added a
UpdatedMerchant
webhook notification for paypoint updates. You can now get a notification when a paypoint’s address, banking information, or funding configuration is updated. See Webhook Notification Response Reference for the webhook payload. - Added the
ReplyBy
field to responses from the Query/chargebacks endpoint. The ReplyBy field is the deadline by which a merchant must respond to a dispute. By default, this field is exactly 10 days after theCreatedAt
timestamp, in UTC. - Added the
replyDate
filter to the Query/chargebacks endpoint which allows filtering disputes by deadline.replyDate
has the following conditions:(gt, ge, lt, le, eq, ne)
. See the Filters and Conditions Reference for more information.