Migration FAQ
Last updated: April 29, 2022
Below you'll find the answers to some of the most frequently asked questions about migration from the Classic API to the Unified Payments API.
Yes you can. To do so, you can call the /refunds
endpoint in the Unified Payments API with the charge ID of the capture. For example:
post
https://api.checkout.com/payments/charge_895B79BD740K67F83D12/refunds
1{2"reference": "ORD-5023-4E89"3}
If you rely on webhooks, you will need to maintain your Classic API webhook handler for the above scenario only. This is because in the above scenario, we will send you Classic API event types.
Yes you can.
Yes you can. The webhook event types that you will receive are governed by the Gateway API used to request the payment. This means that if you request a payment using the Unified Payments API, you will receive only its associated webhook event types.
No, Checkout.js is now deprecated. You should upgrade to our Hosted Payments Page or Frames. You can also read our full Checkout.js migration guide.
Yes, this setup can be configured in particular situations. Please email [email protected] for more details.
Yes you can. The previous_payment_id
field supports payment IDs, charge IDs, as well as scheme IDs.