Refund a captured payment in Adyen Checkout
A documented Adyen Checkout operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Refund a captured payment
- POSTChanges data · Modifications
checkout-test.adyen.com/payments/{paymentPspReference}/refunds
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Adyen Checkout operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Adyen Checkout operations
- Create an orderPOST · changes data
- Create a payment sessionPOST · changes data
- Get a list of available payment methodsPOST · changes data
- Get the list of brands on the cardPOST · changes data
- Create a payment linkPOST · changes data
- Cancel an orderPOST · changes data
- Submit details for a paymentPOST · changes data
- Cancel an authorised paymentPOST · changes data
Questions
- Can HumDay refund a captured payment in Adyen Checkout?
- Yes. This operation is published in Adyen Checkout's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Adyen Checkout data?
- Yes — this is a POST operation, so it changes something in Adyen Checkout. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Adyen Checkout account.
Where this came from
Read from a published API description for Adyen Checkout at raw.githubusercontent.com/Adyen/adyen-openapi/main/json/CheckoutService-v70.json. The description above is the provider’s own wording, not ours. Last published 2023-04-19.