Changes for page Vipps direct API
Last modified by Asbjørn Ulsberg on 2019/07/11 15:00
From version 68.2
edited by Fredrik Köhler
on 2018/09/10 13:17
on 2018/09/10 13:17
To version 69.1
edited by Fredrik Köhler
on 2018/09/10 13:22
on 2018/09/10 13:22
Change comment: There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,13 +1,7 @@ 1 - [[image:vipps_sjgrnn.png||width="150"]]1 +Vipps is a two-phase payment method supported by the major norwegian banks. In the direct API scenario, PayEx receives a mobile number (MSISDN) directly from the merchant UI. PayEx performs a payment that the consumer must confirm in the Vipps mobile app. 2 2 3 -{{toc depth="3"/}} 4 - 5 -= High level = 6 - 7 -Vipps is a payment method supported by the major norwegian banks, where PayEx will receive a mobile number (MSISDN) and perform a payment that the consumer must confirm in the Vipps mobile app. 8 - 9 -* Collect all purchase information and make a POST towards PayEx. 10 -* Collect the consumers mobile number, and make a POST towards PayEx. 3 +* When the consumer/end-user starts the purchase process, you make a POST request towards PayEx with the collected PURCHASE information. 4 +* After that, you need to collect the consumer's mobile number and make a POST request towards PayEx. 11 11 * PayEx will handle the dialogue with Vipps and the consumer will have to confirm the purchase in the Vipps app. 12 12 * Finally you will receive a payment callback when the Vipps dialogue is completed, and you will have to make a GET request to check the payment status. 13 13 * The flow is explained in the picture below: ... ... @@ -116,12 +116,12 @@ 116 116 == Options after posting a payment == 117 117 118 118 * Be prepared to [[receive a CALLBACK from PayEx>>doc:Main.ecommerce.technical-reference.Vipps Callback API Description.WebHome]]. 119 -* VIPPS only support 2.phase transactions (AUTHORIZE), which mean that you must implement the CAPTURE and CANCEL requests.113 +* VIPPS only support two-phase transactions (AUTHORIZE), which mean that you must implement the CAPTURE and CANCEL requests. 120 120 * For reversals, you will need to implement the REVERSAL request. 121 121 122 122 === Capture Sequence === 123 123 124 -Capture can only be done on a authorized transa ction.118 +Capture can only be perfomed on a payment with a successfully authorized transaction. It is possible to do a part-capture where you capture a smaller amount than the authorized amount. You can later do more captures on the same payment up to the total authorization amount. 125 125 126 126 {{plantuml}} 127 127 @startuml ... ... @@ -174,7 +174,7 @@ 174 174 175 175 === Cancel Sequence === 176 176 177 -Cancel can only be done on a authorized transaction. 171 +Cancel can only be done on a authorized transaction. If you do cancel after doing a part-capture you will cancel the different between the capture amount and the authorization amount. 178 178 179 179 {{plantuml}} 180 180 @startuml ... ... @@ -222,11 +222,9 @@ 222 222 @enduml 223 223 {{/plantuml}} 224 224 225 - 226 - 227 227 === Reversal Sequence === 228 228 229 -Reversal can only be done on a capturedtransaction.221 +Reversal can only be done on a payment where there are some captured amount not yet reversed. 230 230 231 231 {{plantuml}} 232 232 @startuml