Transmit a Authorize transaction request on Payment API v2 / Payment Request on Payment API v1 when the buyer agreed to the terms & conditions, confirms the order and you have complete buyer, address, and basket data.
Upon Capture (Payment API v2) or Confirmation Deliver (Payment API v1), i.e., after shipment is initiated.
Yes. Capture (Payment API v2) or transmit the Confirmation Deliver (Payment API v1) only shipped items/quantities. Multiple captures per transaction are supported.
Capture (Payment API v2) or transmit the Confirmation Deliver (Payment API v1) for what is shipped; cancel the remaining items or perform a later capture when stock arrives, as your policy allows.
Use the Incrementally authorize request (Payment API v2) or Payment Change@change-order (Payment API v1) to increase the authorized amount. A new risk check is performed for the increment.
Yes - by capturing fewer items or lower amounts. For v1, use Payment Change@change-order where applicable.
After capture, use the Refund transaction request (Payment API v2) or [Payment Change@return](Payment Change@change-order request (Payment API v1) to return amounts or items. Multiple partial refunds are supported up to the captured total.
Cancellations apply to uncaptured authorizations. After capture, use Refund.
Yes - cancel remaining (not yet captured) items/amounts from the authorization.
Perform multiple captures. Each capture should list the items/quantities included in that shipment.
Authorize when you are ready and have the buyer’s consent; capture when shipping begins. Check authorization validity windows. (Standard: 120 days)
For Payment API v1 transactions, there is directly no expiry date. Ratepay will reach out to you after some time with a list of open transactions to confirm if they will still be delivered or should be cancelled. For Payment API v2, the expiry date will be responded after successful authorization of a transaction. If the time window passes, you may need to re‑authorize or use the Change transaction request, depending on timing and configuration. (Standard: 120 days)
Yes - depending on the decline. See here for further details.
Map technical statuses to user‑friendly messages, which are mentioned here.