diff --git a/_includes/payment-order-cancel-3-1.md b/_includes/payment-order-cancel-3-1.md index d23160285b..acf69036b8 100644 --- a/_includes/payment-order-cancel-3-1.md +++ b/_includes/payment-order-cancel-3-1.md @@ -12,8 +12,9 @@ specific payment. To cancel a previously created payment, you must perform the `cancel` operation against the accompanying `href` returned in the `operations` list. You can only -cancel a payment - or part of a payment - which has not been captured yet. If -you cancel before any capture has been done, no captures can be performed later. +cancel a payment - or part of a payment - which has not been captured yet. There +must be funds left that are only authorized. If you cancel before any capture +has been done, no captures can be performed later. {% else %} diff --git a/_includes/payment-order-cancel-combined.md b/_includes/payment-order-cancel-combined.md index 645a019f5f..8cea091460 100644 --- a/_includes/payment-order-cancel-combined.md +++ b/_includes/payment-order-cancel-combined.md @@ -10,8 +10,9 @@ specific payment. To cancel a previously created payment, you must perform the `cancel` operation against the accompanying `href` returned in the `operations` list. You can only -cancel a payment - or part of a payment - which has not been captured yet. If -you cancel before any capture has been done, no captures can be performed later. +cancel a payment - or part of a payment - which has not been captured yet. There +must be funds left that are only authorized. If you cancel before any capture +has been done, no captures can be performed later. ## Cancel Request (All Versions) diff --git a/_includes/payment-order-cancel.md b/_includes/payment-order-cancel.md index 3a2e78d58a..af14858ab0 100644 --- a/_includes/payment-order-cancel.md +++ b/_includes/payment-order-cancel.md @@ -12,8 +12,9 @@ specific payment. To cancel a previously created payment, you must perform the `cancel` operation against the accompanying `href` returned in the `operations` list. You can only -cancel a payment - or part of a payment - which has not been captured yet. If -you cancel before any capture has been done, no captures can be performed later. +cancel a payment - or part of a payment - which has not been captured yet. There +must be funds left that are only authorized. If you cancel before any capture +has been done, no captures can be performed later. {% else %} diff --git a/_includes/payment-order-capture-3-1.md b/_includes/payment-order-capture-3-1.md index b43b73ed6e..943b0fe86e 100644 --- a/_includes/payment-order-capture-3-1.md +++ b/_includes/payment-order-capture-3-1.md @@ -6,8 +6,9 @@ Captures are only possible when a payment has a successful authorize transaction, naturally excluding one-phase payment instruments like -[Swish][swish] and [Trustly][trustly]. Two-phase payment instruments like -[Card][card] and [Vipps][vipps] however, require a `Capture` to be completed. +[Swish][swish] and [Trustly][trustly]. They will be marked as a `Sale` +transaction. Two-phase payment instruments like [Card][card] and [Vipps][vipps] +however, require a `Capture` to be completed. Please note that you have a maximum of 5 **consecutive** failed attempts at a capture. The payment will be locked after this, and you need to contact us for diff --git a/_includes/payment-order-capture-combined.md b/_includes/payment-order-capture-combined.md index 4b4e46cce5..aced7409fb 100644 --- a/_includes/payment-order-capture-combined.md +++ b/_includes/payment-order-capture-combined.md @@ -6,8 +6,9 @@ Captures are only possible when a payment has a successful authorize transaction, naturally excluding one-phase payment instruments like -[Swish][swish] and [Trustly][trustly]. Two-phase payment instruments like -[Card][card] and [Vipps][vipps] however, require a `Capture` to be completed. +[Swish][swish] and [Trustly][trustly]. They will be marked as a `Sale` +transaction. Two-phase payment instruments like [Card][card] and [Vipps][vipps] +however, require a `Capture` to be completed. Please note that you have a maximum of 5 **consecutive** failed attempts at a capture. The payment will be locked after this, and you need to contact us for diff --git a/_includes/payment-order-capture.md b/_includes/payment-order-capture.md index 84779711a3..7dbfb6ff04 100644 --- a/_includes/payment-order-capture.md +++ b/_includes/payment-order-capture.md @@ -14,8 +14,9 @@ Captures are only possible when a payment has a successful authorize transaction, naturally excluding one-phase payment instruments like -[Swish][swish] and [Trustly][trustly]. Two-phase payment instruments like -[Card][card] and [Vipps][vipps] however, require a `Capture` to be completed. +[Swish][swish] and [Trustly][trustly]. They will be marked as a `Sale` +transaction. Two-phase payment instruments like [Card][card] and [Vipps][vipps] +however, require a `Capture` to be completed. Please note that you have a maximum of 5 **consecutive** failed attempts at a capture. The payment will be locked after this, and you need to contact us for diff --git a/_includes/payment-order-reversal-3-1.md b/_includes/payment-order-reversal-3-1.md index df7bf6af1c..4b5a8c0c20 100644 --- a/_includes/payment-order-reversal-3-1.md +++ b/_includes/payment-order-reversal-3-1.md @@ -7,7 +7,8 @@ ## Reversal v3.1 -This transaction is used when a captured payment needs to be reversed. +This transaction is used when a `Capture` or `Sale` payment needs to be +reversed. Please note that you have a maximum of 5 **consecutive** failed attempts at a reversal. The payment will be locked after this, and you need to contact us for diff --git a/_includes/payment-order-reversal-combined.md b/_includes/payment-order-reversal-combined.md index e13f3b9e6d..2e657f4db1 100644 --- a/_includes/payment-order-reversal-combined.md +++ b/_includes/payment-order-reversal-combined.md @@ -5,7 +5,8 @@ ## Reversal -This transaction is used when a captured payment needs to be reversed. +This transaction is used when a `Capture` or `Sale` payment needs to be +reversed. Please note that you have a maximum of 5 **consecutive** failed attempts at a reversal. The payment will be locked after this, and you need to contact us for diff --git a/_includes/payment-order-reversal.md b/_includes/payment-order-reversal.md index 03452bc757..1ddd013a6f 100644 --- a/_includes/payment-order-reversal.md +++ b/_includes/payment-order-reversal.md @@ -7,7 +7,8 @@ ## Reversal -This transaction is used when a captured payment needs to be reversed. +This transaction is used when a `Capture` or `Sale` payment needs to be +reversed. Please note that you have a maximum of 5 **consecutive** failed attempts at a reversal. The payment will be locked after this, and you need to contact us for diff --git a/checkout-v3/get-started/index.md b/checkout-v3/get-started/index.md index f4139ff5f7..f8d7df039f 100644 --- a/checkout-v3/get-started/index.md +++ b/checkout-v3/get-started/index.md @@ -39,6 +39,14 @@ payment, **displaying** the payment UI, **verifying** the payment status and **post-purchase actions**. Don't hesitate with contacting us for further integration support. +Depending on the instrument used, the payments are either **one-phased** or +**two-phased**. **Swish** and **Trustly** have one-phase payments, the rest of +the instruments are two-phased. One-phase payments are completed and the funds +are transferred in one operation. They will be tagged as `Sale` transactions. +Two-phase payments need two operations (`Authorization` and `Capture`) before +funds are transferred. Read more about differences in handling when you get to +the [post-purchase section][post-purchase]. + ![Implementation steps][basic-implementation]{:class="mt-4 mb-5"} {:.table .table-plain} @@ -97,6 +105,7 @@ when we get there. [migrate]: /checkout-v3/migration-guide/ [modules-sdks]: /checkout-v3/modules-sdks/ [nwt]: /checkout-v3/features/optional/network-tokenization/ +[post-purchase]: /checkout-v3/get-started/post-purchase-3-1/ [rest]: https://en.wikipedia.org/wiki/Representational_state_transfer [set-rec]: /checkout-v3/features/core/settlement-reconciliation/#report-samples [test-cards]: /checkout-v3/test-data/#network-tokenization