Frequently asked questions

Here are the Checkout API FAQs. See the Checkout API guide for more details.

For general information and questions, please check in the Knowledge base.

General Information

What is Checkout?

Checkout is an online payment solution that allows businesses to offer their customers a fast, secure, and convenient way to pay for goods and services online.

How do I sign up for Checkout?

To sign up for Checkout, you need to create an account on the Vipps website and follow the instructions to set up your account. You will need to provide information about your business and bank account details.

What kind of support is available for Checkout users?

We provide support through our website, email, and through our extensive partner network. There is also a knowledge base available on the website that contains answers to frequently asked questions.

Payment Methods

Which payment methods are available with Checkout?

	Vipps	MobilePay	Card	Bank transfer (bank button)
Norway	✅		✅
Denmark		✅	Coming soon
Finland		✅	Coming soon	✅

Please note: Bank transfer must be enabled by the merchant during the Checkout onboarding flow.

Can I use Checkout for recurring payments?

Checkout works with one-time-payments as well as subscriptions. The merchants must have a valid sales unit with subscription feature enabled.

Security and Fees

Is it safe to use Checkout for online payments?

Yes, Checkout is a secure payment solution that uses industry-standard encryption to protect your and your users' personal and financial information.

What fees are associated with using Checkout?

Checkout charges a percentage fee for the payment volume processed. Our standard prices can be found on vipps.no.

Integration and Functionality

Can I integrate Checkout with my existing website or online store?

Yes, Checkout can be integrated with most major website and e-commerce platforms, including Shopify, WooCommerce, and Magento. Check out our list of plugins for more information.

How long does it take for payments to be paid out with Checkout?

You will typically get your money on your account within three (3) banking days. So money paid to you on a Monday will be on your account on Wednesday, and payment on Friday will be on your account on Tuesday. See Settlements for more details.

How does Checkout compare to other online payment solutions?

Checkout works with card payments, user information retrieval, and shipping selection all in one well-designed bundle, and compares favorably to other online payment solutions.

Technical information

Is it possible to add a newsletter option in Checkout?

Yes, custom consent can be used.

How can I prefill my customers phone number in the payment page (landing page)?

Yes, check out the prefill customer data feature.

Capture, reservations, and refunds

How are subsequent transaction operations (Capture/Cancel/Refund) handled?

All subsequent transaction operations are fully supported in the ePayment API.

See the Knowledge base for common questions about captures, reservations, and refunds.

Testing

I can't test card payments in Merchant Test (MT) environment, is there something wrong?

We currently don't support card payments in test environment, only payments using the MT app. If you need to do verification, we suggest doing a NOK 1 payment in production, and do a subsequent refund, which will make the funds available again within a week.

The only difference between a wallet payment and card payment is that paymentMethod is Wallet or Card.

Card payments

See: Card payments

Shipping

Can I have "Pick-up in store" as shipping option with Checkout?

Yes.

Checkout will basically display whatever shipping methods defined by the webshop. For example, if you want Checkout to display "Pick up at the Royal Norwegian Castle", we will display that upon receiving that message through the API.

For WooCommerce-based web shops, this is done in the shipping configuration part of WooCommerce admin: https://[_your webshop URL_]/wp-admin/admin.php?page=wc-settings&tab=shipping

Errors

Note: our error message format may evolve, so avoid building strict logic around it

Any errors that occur will return a non-successful response code with a body based on Problem Details for HTTP APIs.

Common errors include:

• Invalid credentials (status code 401)
• Missing mandatory fields in a request (status code 400)
• Session expired or not known (status code 404).

An example of error returned when querying an expired session:

{
    "errorCode": "Session-00100",
    "title": "Session expired or not known.",
    "status": 404,
    "instance": "urn:uuid:d1bb89d3-50ab-4e90-94c0-54a67da0a7ec",
}

Example of the result of a failed validation:

{
    "errorCode": "Validation-00001",
    "title": "One or more validation errors occurred.",
    "status": 400,
    "instance": "urn:uuid:d1bb89d3-50ab-4e90-94c0-54a67da0a7ec",
    "errors": {
        "Transaction.Reference": [
            "The Reference field is required."
        ]
    }
}