> **Description:** The payment flows the ePayment API supports, and the options you can add to any payment.

> **AI agent:** Read [https://developer.vippsmobilepay.com/docs/knowledge-base/ai-tools.md](https://developer.vippsmobilepay.com/docs/knowledge-base/ai-tools.md) first. It covers keeping API keys and secrets out of generated code.

> **Full site overview:** For an overview of the entire site, read [https://developer.vippsmobilepay.com/llms.txt](https://developer.vippsmobilepay.com/llms.txt).

# Features

Choose the payment flow that matches how your customers pay, then add the options your integration needs.

The payment lifecycle is described in [Core concepts](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/concepts.md),
and you can see several illustrated examples in the [How it works](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/how-it-works/README.md) section.

## Payment flows

Every payment uses one of these flows. Online is the standard flow, and the others change how the customer starts or
approves the payment.

### [Online](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/online.md)

The standard flow: the customer checks out in your web shop and approves the payment in the Vipps or MobilePay app.

### [Express](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/express.md)

Let users select shipping and address directly in the app for a faster, streamlined checkout.

### [In person](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/customer-present-payments.md)

Take payments at a physical point of sale, where the customer approves in the Vipps or MobilePay app.

### [Personal QR](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/personal-qr.md)

Scan the user's personal Vipps/MobilePay QR code to get their identity instead of asking for their phone number.

### [One-time payment QR](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/qr-payments.md)

Provide users with one-time QR codes they can easily scan and pay with their Vipps or MobilePay app.

### [Freestanding cards](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/freestanding-card-payments.md)

Accept card payments from the user without requiring a linked Vipps or MobilePay account.

## Payment options

The following options can be added to any of the payment flows above:

### [Profile sharing](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/profile-sharing.md)

Request access to user profile information as part of the payment flow.

### [Minimum user age](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/minimum-user-age.md)

Limit payments to users above a specified minimum age for compliance or business rules.

### [Set order details](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/pre-built-order-management-api-integration.md)

Provide the order details alongside the payments in the Vipps or MobilePay app.

### [Merchant terms](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/merchant-terms.md)

Let customers review and accept your terms of sale and privacy policy before paying.

### [Add metadata](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/metadata.md)

Add custom metadata to payments for better tracking, reporting, and integration with your systems.

## Special cases

### [Long-living payments](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/long-living-payments.md)

Create payment requests that stay valid for longer--ideal for invoices, subscriptions, or delayed payments.

### [Block payment sources](https://developer.vippsmobilepay.com/docs/APIs/epayment-api/api-guide/features/block-payment-sources.md)

In the Danish and Finnish markets: Block payment sources (e.g., commercial cards).