From version 80.6
edited by Fredrik Köhler
on 2018/10/15 14:13
To version 80.7
edited by Fredrik Köhler
on 2018/10/26 14:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -21,16 +21,16 @@
21 21  (% id="HOptionsbeforepostingapayment" %)
22 22  === Options before posting a payment ===
23 23  
24 -All valid options when posting a payment with operation equal to Purchase, are described in [[the technical reference>>https://developer.payex.com/xwiki/wiki/developer/view/Main/ecommerce/technical-reference/viabill-payments/]].
24 +All valid options when posting a payment with operation equal to Purchase, are described in [[the technical reference>>doc:Main.ecommerce.technical-reference.core-payment-resources.vipps-payments.WebHome]].
25 25  
26 26  (% id="HTypeofauthorization28Intent29." %)
27 27  ==== Type of authorization (Intent). ====
28 28  
29 -* **Authorization (two-phase)**: The intent of a Vipps purchase is always ##Authorization##. The amount will be reserved but not charged. You will later (i.e. if a physical product, when you are ready to ship the purchased products) have to make a [[Capture>>https://developer.payex.com/xwiki/wiki/developer/view/Main/ecommerce/technical-reference/vipps-payments/#HCaptures]] or [[Cancel>>https://developer.payex.com/xwiki/wiki/developer/view/Main/ecommerce/technical-reference/vipps-payments/#HCancellations]] request.
29 +* **Authorization (two-phase)**: The intent of a Vipps purchase is always ##Authorization##. The amount will be reserved but not charged. You will later (i.e. if a physical product, when you are ready to ship the purchased products) have to make a [[Capture>>doc:Main.ecommerce.technical-reference.core-payment-resources.vipps-payments.WebHome||anchor="HCaptures"]] or [[Cancel>>doc:Main.ecommerce.payex-payment-instruments.vipps-payments.WebHome||anchor="HCancellations"]] request.
30 30  
31 31  ==== General ====
32 32  
33 -* **Defining CallbackURL**: When implementing all scenarios, it is required that you set a CallbackURL in the POST request. PayEx will send a postback request to this URL when the consumer has fulfilled the payment. [[See the Callback API description here.>>url:https://developer.payex.com/xwiki/wiki/developer/view/Main/ecommerce/technical-reference/#HCallback]]
33 +* **Defining CallbackURL**: When implementing all scenarios, it is required that you set a CallbackURL in the POST request. PayEx will send a postback request to this URL when the consumer has fulfilled the payment [[See the Callback API description here.>>doc:Main.ecommerce.technical-reference.WebHome||anchor="HCallback"]]
34 34  
35 35  == Payment flow ==
36 36  
... ... @@ -125,10 +125,10 @@
125 125  
126 126  == Options after posting a payment ==
127 127  
128 -* **Abort:** It is possible to [[abort a payment>>https://developer.payex.com/xwiki/wiki/developer/view/Main/ecommerce/technical-reference/vipps-payments/#HAbort]] if the payment has no successful transactions.
128 +* **Abort:** It is possible to [[abort a payment>>doc:Main.ecommerce.technical-reference.WebHome||anchor="HAbort"]] if the payment has no successful transactions.
129 129  * Vipps only support two-phase transactions (##Authorize##), which mean that you must implement the Capture and Cancel requests.
130 130  * For reversals, you will need to implement the Reversal request.
131 -* **Callback from PayEx:** Whenever changes to the payment occur a [[Callback request>>https://developer.payex.com/xwiki/wiki/developer/view/Main/ecommerce/technical-reference/vipps-payments/#HCallback]] will be posted to the callbackUrl, generated when the payment was created.
131 +* **Callback from PayEx:** Whenever changes to the payment occur a [[Callback request>>doc:Main.ecommerce.technical-reference.WebHome||anchor="HCallback"]] will be posted to the callbackUrl, generated when the payment was created.
132 132  
133 133  === Capture Sequence ===
134 134  

Tips

If you're starting with XWiki, check out the Getting Started Guide.

Need help?

If you need help with XWiki you can contact: