Until now, a Worldpay payment could not be refunded, captured, or released through FloPay. Refunds had to be made in Worldpay's own console, where FloPay's records never saw them. The Worldpay Corporate Gateway connector is still in Preview, and the same payments API calls you use for Stripe payments now work for Worldpay payments too, once Flo Payments Operations approves each operation for your merchant code and environment.
What changed
POST /v1/payments/:id/refundissues full and partial refunds of a Worldpay payment through the Worldpay account that took it. A Worldpay refund stayspendingorprocessinguntil Worldpay confirms it, and the payment's own status changes only once the refund settles.PUT /v1/payments/:id/capturecaptures the full authorized amount, andPUT /v1/payments/:id/cancelreleases the hold. While Worldpay is still confirming, the payment is returned asauthorized. Partial and multiple capture are not supported.- Each refund, capture, or release is sent to Worldpay at most once. Retries, timeouts, and lost answers never send a second one: FloPay confirms the outcome from Worldpay's notification or an exact-order inquiry.
- A settled refund sends one
item.refunded, a successful capture sendsitem.purchased, a failed capture sends onepayment.capture_failed, and a settled release sends onepayment.authorization_voided, with the same payloads as for Stripe and once per outcome. - An operation that is not approved for your merchant code returns
409before anything is sent to Worldpay. - Chargebacks, chargeback reversals, dispute stages, and refunds made in Worldpay's console converge to FloPay's records when Operations has approved that event type. Unapproved event types are held for review.
Developer notes
No endpoint, request field, response field, or status value is added. Stripe and PayPal refunds, captures, and cancellations behave as before.
Read Refunds, capture, and release in the Worldpay connector guide for eligibility, examples, retry rules, and troubleshooting.