v1
latestOpenAPI 3.0.12026-07-2353480642.4 KBInitiate a Vipps payment
Initiate a Vipps payment.
Headers
A value you specify that uniquely identifies this transaction. This must be used to trigger a reversal if there is a timeout.
Request body
The identifier of payment provider contract you want to process the transaction request with.
The Phone Number registered with Vipps Mobile APP.
Checkout Redirect URL which will be used by Vipps on Payment Completion.
Flag to identify the transaction originated from APP or Browser.
Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
Flags a payment request for either pre-authorization or final authorization.
- PRE_AUTH is used when the authorized amount is unknown and can be adjusted later.
- FINAL_AUTH is used when a final authorized amount is known and the transaction will definitely be captured in whole.
Whether auto-capture or not. Setting the value to 'false' will only authorize the transaction.
The ID of a customer.
A short descriptor to be shown on bank statement of the customer. Please refer to the integration guide for the format requirements.
A reference specified by the merchant to identify the transaction.
The full user agent string of the device the customer used to submit the transaction.
A reference used by the merchant to typically capture a description of the service provided. It could then be used by the merchant to help locate transactions. One could envision a situation where a merchant is trying to locate a transaction/ receipt but in speaking with the customer, the only (or at least a predominant) detail is what service was rendered
Three-letter ISO 4217 alphabetical currency code. e.g. USD. Values correspond to ISO 4217.
Please note that Klarna only supports Norwegian krone (NOK).
- NONE: No SCA required.
- WALLET: Depend on the wallet SCA mechanism. For Google Pay this means that MasterCard will shift liability, Visa will not.
- FORCE_3DS: Do an additional 3DS step regardless of whether the wallet indicates the token is SCA-compliant.
Use this field to request your transaction to be exempted from the application of the Strong Customer Authentication (SCA). Be advised that the use of this field may result to your liability in case of fraudulent transaction. Possible Values: 1 - Low value payment 2 - Acquirer Transaction Risk Analysis 3 - Trusted beneficiary exemption 4 - Secure Corporate Payment (SCP) exemption 5 - Merchant Initiated Transaction 6 - SCA Delegation.
NOTE: This only applies when sca_compliance_level = NONE
Response
The Vipps Payment Initiation Response.
The ID of the transaction.
Vipps Host Redirection URL.
Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
True if the transaction has been blocked by a ruleset, false otherwise
The time at which the transaction was created.
The ID of a customer
A reference specified by the merchant to identify the transaction.
The name of the processor used for this transaction
The payment product corresponding to this transaction
The payment product type corresponding to this transaction. Fees applied to the transaction, is based on the payment product
The outcome of the payment request.
Message provided by the 3rd party service as additional information, when the transaction does not succeed.
The ID of the user who initiated the transaction. Only set when shopper_interaction = moto, mail_order or telephone_order
Determines the sales channel the shopper gives their card details through:
-
ECOMMERCE Online transactions where the cardholder is present.
-
MAIL order transactions where the shopper is in contact with the merchant via email.
-
TELEPHONE order transactions where the shopper is in contact with the merchant via telephone.
The latitude / longitude resolved from the customer's ip address.
The city resolved from the customer's ip address.
The ISO 3166-1 alpha-2 country code.<blockquote><strong>Note:</strong> The country code for Great Britain is <code>GB</code> and not <code>UK</code> as is used in that country's top-level domain names.</blockquote>.