> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# Vipps/MobilePay

> Request accounting partner API credentials from your Vipps/MobilePay account manager, then add the integration in the Portal.

This guide explains how to obtain your Vipps/MobilePay **accounting partner** API credentials and connect Vipps/MobilePay as a data source in Payrails to ingest funds, fees, and payout data. With the self-serve flow, you configure the integration yourself in the Payrails portal.

## Prerequisites

* An active Vipps/MobilePay merchant account
* A point of contact who can provision **accounting partner** API access, such as your Vipps/MobilePay account manager or **accounting partner** administrator

## Overview

Payrails ingests Vipps/MobilePay data through the **Report API** using **accounting partner** credentials. Do not use the merchant sales unit API keys used for taking payments. **Accounting partner** credentials use OAuth2 client credentials and provide read-only access to funds and fee reports across all of your merchant's ledgers, so you need one credential pair regardless of the number of currencies or ledgers you operate.

## Step-by-step instructions

### Step 1: Request accounting partner API credentials from Vipps/MobilePay

1. Contact your Vipps/MobilePay account manager or accounting partner administrator.
2. Request an **accounting partner** Client ID and Client Secret with read-only **Report API** access for funds and fee reports.
3. Store the credentials securely after Vipps/MobilePay provisions them. Treat the Client Secret like a password, since you typically cannot retrieve it again later.

### Step 2: Add the Vipps/MobilePay integration in the Payrails portal (self-serve)

1. Log in to the Payrails dashboard and open **Settings → Integrations → Data**.
2. Click **Add instance** (top-right).
3. In **New instance**, select provider: **Vipps/MobilePay** and click **Continue**.
4. On the **Configure account** screen, fill in:
   * **Integration instance name**: a unique label.
   * **Start Date**: the date of today or tomorrow. Payrails cannot backfill data through the self-serve flow. Contact your Payrails account manager if you need historical data.
   * **Client ID**: your Vipps/MobilePay **accounting partner** Client ID.
   * **Client Secret**: your Vipps/MobilePay **accounting partner** Client Secret. Payrails stores this value masked.
5. Click **Save account**. The instance appears in the Data integrations list, and Payrails begins ingesting data.


## Related topics

- [Connect your data sources](/docs/analytics-and-reporting/getting-started/connect-your-data-sources/index.md)
- [MobilePay](/docs/orchestration/payment-methods/mobilepay.md)
- [Mobile Wallets](/docs/orchestration/payment-methods/mobile-wallets.md)