Force Approve a payment

View as Markdown (opens in a new tab)

Install AI tools

Our plugin gives your assistant up-to-date guidance for payments and login. Full instructions

Claude Code

Run both commands, in order.

claude plugin marketplace add vippsas/agent-toolkit
claude plugin install vipps@agent-toolkit

Cursor

Open Settings, then Plugins.

Add vippsas/agent-toolkit as a plugin marketplace, then install the "vipps" plugin.

Codex

See the Codex plugin docs at developers.openai.com/codex.

Add vippsas/agent-toolkit as a plugin marketplace, then install the "vipps" plugin.

Any editor

No plugin needed. Paste this into your assistant.

Read https://developer.vippsmobilepay.com/llms.txt for the Vipps MobilePay developer documentation.

All ePayment API requests must include a valid Bearer token in the Authorization header. See Authorization for how to obtain one.

To simplify automated testing in the test environment the ePayment API provides a "force approve" endpoint that confirms payments without using the test app: POST:/epayment/v1/test/payments/{reference}/approve.

Express is not supported for this endpoint. Attempted use in production is not allowed, and will fail. Important: All test users must manually approve at least one payment in the Vipps or MobilePay app before this endpoint can be used for that user.

You may get HTTP 500 Internal Server Error for an expired card. If this is the case, you should create a new test user.

Here are the expected properties for the request body:

	Customer phone number (object) or Personal QR code (object) or Customer token (object) (Customer) The target customer if the identity is known. The customer can be specified either with phone number, the customer token or with the user's personal QR code Specifying more than one of these will result in an error.
token	string The token value received in the redirectUrl property in the Create payment response

See the API spec for more details.