Vipps
Checkout can be used to accept Vipps payments.
Integration options supported: Hosted payment page (HPP) or IFRAME.
This guide requires familiarity with Accepting payments.
Integrate Vipps via Checkout
currency_code
String (required)
Supported currencies: NOK
amount
Integer (required)
Transaction amount
customer
String (required)
ID of a customer created via the Customer API. A customer object can be created and attached to a Checkout.
configurations.vipps
Object (required)
Object carrying the parameters required for making a Vipps payment
payment_contract_id
String (required)
This ID can be found in the portal or given to you by a Verifone employee. It is used to retrieve a merchant's Vipps credentials necessary for payment.
dynamic_descriptor
String (optional)
Short text to be displayed on the bank statement of the cardholder. Support varies per Payment Contract.
capture_now
Boolean (optional)
Used for separate authorization and capture
is_app
Boolean (optional)
Flag to identify the transaction originated from APP or Browser
app_phone_number
String (optional)
Indicates the phone number, without country code, registered with Vipps Mobile APP. Supported value: 8 digits without spaces.
card
Object (optional)
Details regarding SCA compliance Required, 3DS Required and authorization type Required
authorization_type
String (optional)
Card Authorization Type (PRE_AUTH, FINAL_AUTH). When capture_now is set to true, pre-authorization transactions cannot be done.
Authorization and capture
You can use Vipps transactions through the Checkout to do a sale (capture_now = true) or to authorize without capturing immediately (capture_now = false). An authorized payment reserves the money and allows you to capture the funds at a later stage.
Sending a checkout request using Vipps payment method:
Handling responses
Whenever a card payment is processed via the Checkout, the responses events include additional parameters specific to card payments in the details object.
Example of a successful Vipps payment via the Checkout:
Example of a failed Vipps payment via the Checkout:
To ensure that the redirection request was not tampered with, always check that the
transaction_idreceived as query parameter in the redirection matches thetransaction_idproperty of the retrieved Checkout. If those are not matching, this is indication of either an incorrect integration, that the redirection to yourreturn_urldid not originate from Verifone, ortransaction_idwas tampered with.You can now store the
transaction_idvalue together with the order 1234 in your system to link the two together.
Scenarios
The table below describes the different outcomes of a Checkout. A full list of error codes is available.
Description
Result
Merchant action
Failed transaction*
Redirect: checkout_id={checkout_id} & transaction_id={transaction_id} & errorCode=123
Unsuccessful payment (technical reason), do not display order confirmation
Successful transaction
Redirect: checkout_id={checkout_id} & transaction_id={transaction_id}
Display order confirmation
Customer visits the URL of an already completed Checkout
Redirect: checkout_id={checkout_id} & errorCode=168
Display corresponding message to the customer. Checkout is completed whenever there was a single successful payment processed through it.
Customer visits the URL of an expired Checkout
Redirect: checkout_id={checkout_id} & errorCode=169
Display corresponding message to the customer. Checkout is expired whenever the expiry_time is reached
Customer visits the URL of a Checkout which has reached the maximum of failed payment attempts
Redirect: checkout_id={checkout_id} & errorCode=165
Display corresponding message to customer. Payments through a single Checkout can be attempted up to three times unsuccessfully.
Form validation errors / Other service failures on the Checkout page
Displays error alert to Customer on the page
Customer is prompted to correct their form input and retry the payment or try using alternate card or payment method
*** Failed transaction - Depending on which step in the payment process failed, the transaction_id might not always be present as the query parameter
Last updated
Was this helpful?
