# Breaking changes to partial payments API preview

If you're using the partial payments API preview to partially pay invoices, you may need to make some changes to your integration to accommodate for upcoming breaking changes to the APIs before 3/30/2025. Below is guidance on what's changing and what you may need to update in your integration.
**What’s changing**
Based on user feedback, we’re updating the API as we prepare for general availability. Two breaking changes may impact your integration:
1. We’re moving `amount_overpaid` from the InvoicePayment resource to the Invoice object as `invoice.amount_overpaid`.
1. We’ll start including out-of-band payments (payments made outside of Stripe) in the InvoicePayment resource. If you’ve been using out-of-band payments to mark invoices as partially or fully paid, you’ll now see these in the InvoicePayment resource.
**What you need to do**
Update your integration by March 30, 2025.
1. If you are reading `amount_overpaid` from the InvoicePayment resource, you'll need to start reading `invoice.amount_overpaid` on the [Invoice object](https://docs.stripe.com/api/invoices/object#invoice_object-amount_overpaid) instead.
1. If you are listening to the `invoice.payment.overpaid` [event](https://docs.stripe.com/api/events/types#event_types-invoice.overpaid), you'll need to start listening to the `invoice.overpaid` event instead.
1. If you're currently expecting the InvoicePayment resource to exclude any out-of-band payments, you may need to filter these out using the `payment.type` field on the [InvoicePayment resource](https://docs.stripe.com/api/invoice-payment/object#invoice_payment_object-payment-type).