Skip to main content

Settlements

When you capture a payment, Vipps MobilePay batches your transactions and transfers the funds to your bank account. Understanding how this works helps with cash flow planning, accounting reconciliation, and spotting discrepancies quickly.

The settlement process adheres to our terms and conditions.

Settlement frequency​

Choose the frequency that fits your cash flow and reconciliation needs:

FrequencyCalculation timeBest for
DailyEvery day at midnight, including weekends and bank holidaysHigh-volume merchants who need funds quickly
WeeklyEvery MondayBusinesses that reconcile weekly
MonthlyFirst day of the monthBusinesses that reconcile monthly or prefer fewer bank entries
info

You can change the settlement frequency yourself on the business portal — no approval required, as long as there are no risk factors on the account. Select your sales unit in the sidebar to see its settings, then click Edit in the Settlement section.

Accounting graphic

Settlement flow​

Settlements can occur at daily, weekly, or monthly intervals. Settlement reports are available within a few hours after the settlement (one file every day).

Payments are processed every day, but the banks may not book them until the next banking day. For example, the payout for Friday, Saturday, and Sunday arrive as three separate transactions and each payout has a separate settlement file.

There is only one payout per settlement period. Even if there have been thousands of payments in one week, there will still only be one payment (e.g., lump sum) from us to the merchant. The settlement reports have all the details for each of the thousands of payments. Additionally, there is one payment per sales unit and this includes a corresponding settlement file.

The daily settlement flow for Vipps is as follows:

  • Day 1:
    • The payment is captured.
    • At midnight: We calculate the settlement.
  • Day 2: We make the settlement data available (See How to get settlement data).
  • Day 3: We send the payment to the merchant's bank account. The bank may not book it until the next banking day.

For example:

  • Monday capture results in a Wednesday payment
  • Friday capture results in a Tuesday payment

Money is normally available in the account before noon.

piggy bank

Understanding your bank transfer​

Your bank statement shows a single lump sum from Vipps MobilePay per sales unit per settlement period — not a line per transaction. This section explains how to trace that transfer back to the individual payments behind it.

Each settlement period produces a single payout — a lump sum transferred from Vipps MobilePay to your bank account (see Settlement flow). Your bank statement will show one transfer per sales unit per settlement period, not a separate line for each individual payment.

Bank reference text​

Each transfer includes a reference text that you can use to identify it.

Norway

Format: Utb. {Recipient} Vippsnr {PayoutNumber}

Example: Utb. 2000810 Vippsnr 117703

This format is not configurable.

Denmark and Finland

Default format: 02{Recipient:08}001{DD}{MM}{YY}{C}

The format can be customized on the business portal on the Details page for the sales unit.

note

Vipps MobilePay sends the reference text to your bank, but has no control over how your bank displays it in online banking or printed statements.

Finding the payments behind a payout​

Once you have identified the payout reference in your bank statement, you can find the individual payments that make up that transfer:

  • Without the Report API: Download the settlement report from the business portal (Reports section). In the report, Payout scheduled rows include a Payout number column. The payment rows surrounding a Payout scheduled entry belong to that payout.
  • With the Report API: The reference field on a payout-scheduled entry in the funds feed matches the reference text on your bank statement. See the Report API FAQ — Bank payouts for details and an example.

How to get settlement data​

You can get the settlement data in these ways:

info

The SFTP service was shut down on 2024-07-01. Please use the Report API to get data programmatically.

Get data through the Report API​

Use the Report API to get your settlement data programmatically. With this API, you can get daily or continuous-feed settlement data for your accounts. See the Report API guide for details.

Download settlement reports​

You can download reports from the business portal in the Reports section.

If the Personal information option is selected in the download dialog, the report may include personal details of customers. Please consider GDPR.

New reports​

New default format

This is the default report format in the business portal. The legacy reports are still available for backwards compatibility.

The new report format is:

  • Simpler
  • More flexible, with customizable options
  • A more complete and transparent reflection of account activity, especially helpful if unexpected events occur
  • Better aligned with the Report API
  • Uniform across all markets
  • Faster to download, especially for large files

Good to know about the new reports:

  • The Details sheet in xlsx and the csv export present account activity as a chronological list. This makes it easier to trace the sequence of events for troubleshooting or reconciliation.
  • The report includes all activity for the selected days, regardless of whether payouts have been scheduled on those days. For example, if today is included in the report period, you'll see today's transactions even if a payout hasn't been processed yet.
  • A single report can cover multiple sales units. Entries are ordered first by sales unit and then chronologically by time.
  • The report can be configured to include only payouts. This can be helpful (and much faster to generate) for sales units with high transaction volumes that are only interested in payouts.
Formats​
XLSX​

xlsx is best for overview, reconciliation, and spreadsheet work. It contains a Summary sheet and a Details sheet. The sheets are set up as Excel tables, so they work well as a source for pivot tables, and each column can be filtered and sorted on right away.

CSV​

csv is best for imports and data processing. It's equal to the Details sheet in xlsx.

Summary sheet​

The Summary sheet gives a simple overview for each sales unit and booking date, including captures, refunds, fees, payouts, and any remaining end-of-day balance. The totals row at the bottom updates automatically when you filter the table. At the top of the sheet, there is also a short preamble with report information such as the company, reporting period, when the file was generated, and the timezone used in the report.

These are the columns in the Summary sheet:

Column nameDescription
Sales unitThe name of the sales unit.
MSN/Vipps number or MSN/MobilePay numberMSN for ePayment sales units; Vipps number (Norway, Sweden) or MobilePay number (Denmark, Finland) for others. The column name varies by market.
Booking dateThe date this summary covers.
CountryThe country that the sales unit operates in.
CurrencyThe currency used.
Capture countThe number of captures on that date.
Refund countThe number of refunds on that date.
CapturesThe total amount captured on that date.
RefundsThe total amount refunded on that date.
FeesThe total fees for that date.
OtherOther entries for that date, such as corrections or top-ups.
PayoutThe amount paid out on that date, when applicable.
Remaining balanceThe balance remaining after that booking date.
Fee statusWhether fees were retained or invoiced. The cell is blank if that date's fees have not yet been retained or invoiced.
Payout referenceThe payout reference text.
Payout bank accountThe bank account used for the payout.
Scheduled payout dateThe date the payout is scheduled to be executed.
RemarksExtra information for exceptional cases, such as dates that are not yet closed.
Details sheet​

These are the columns in the Details sheet in the xlsx and csv formats:

Column nameDescription
Sales unitThe name of the sales unit.
MSN/Vipps number or MSN/MobilePay numberMSN for ePayment sales units; Vipps number (Norway, Sweden) or MobilePay number (Denmark, Finland) for others. The column name varies by market.
CountryThe country that the sales unit operates in.
Payment solutionThe payment solution used for the transaction, e.g., Checkout, Shopping basket.
TimeThe timestamp for the entry, in the timezone specified in the preamble on the Summary sheet.
Booking dateThe date the entry is booked on.
TypeEntry type (see below).
AmountTransaction amount. The sign of the amount indicates how it affects the balance. For instance, a Capture increases the balance, while a Payout scheduled decreases it.
BalanceThe balance after the transaction, representing the running amount owed by Vipps MobilePay to the sales unit. It can be negative if the sales unit currently owes Vipps MobilePay money (e.g. after large refunds). The balance is typically reset to zero when a payout is scheduled.
FeeThe fee for the transaction.
Net amountThe amount after fees for the entry.
CurrencyThe currency of the transaction.
Customer nameThe full name of the customer.
Customer phone numberThe masked phone number of the customer: country code and last four digits are visible (e.g., +47 xxxx 5678).
MessageThe customer's message for the transaction.
CategoryThe transaction's category for Open amount payment solutions (when configured).
PSP referenceVipps MobilePay's reference for the entry (equals pspReference in the Report API).
Order ID/ReferenceOrder ID for Vipps/MobilePay numbers; the merchant's own reference for ePayment transactions (equals reference in the Report API).
Payout numberFor Payout scheduled entries.
Payout bank accountThe bank account number for payouts. For Payout scheduled entries.
Scheduled payout dateThe date the payout is scheduled to be executed. For Payout scheduled entries.
Entry types​

Each entry has one of the types described below. These correspond to the Funds entry types returned by the Report API. Additional types may be introduced in the future without prior notice; such updates will not be considered breaking changes.

TypeDescription
CapturePayment from a customer to the merchant; increases the balance.
RefundRefund from the merchant to a customer; decreases the balance.
Payout scheduledScheduled payout from Vipps MobilePay to the merchant. Typically we pay out the entire outstanding balance, which resets it to zero.
Fees retainedAmount retained by Vipps MobilePay to cover fees (includes capture and other fees); decreases the balance. Note: If you pay fees by invoice, they are not shown on this report.
Invoiced top-upDeposit by the merchant to Vipps MobilePay to cover a negative balance; increases the balance. This entry appears when the invoice is issued, not when it is paid.
Credit noteCredit for a previously issued top-up invoice; decreases the balance.
CorrectionManual adjustment to the balance (may be positive or negative).
Example files​

Legacy reports​

The legacy report format is still available for backwards compatibility. These reports are only available for the Norwegian market, in several formats:

PDF - Settlement report with key figures for the period you've selected.

For example:

Settlement report availability​

Settlement reports are available within a few hours after the settlement.

Daily settlement reports are created every day (one file every day), as long as the balance is positive (see Download reports from the business portal).

If the balance for a day is zero (e.g. due to lack of transaction) or negative (e.g. due to refunds), a settlement will not be created until the balance becomes positive. This means that in some cases, a settlement report may include transactions spanning several days back in time.

Settlement reports are available by 12:00 noon. The reports are generated around 01:00-03:00 at night, but may be delayed due to technical changes, maintenance in various systems, or other unforeseen events.

note

There will be no settlement reports for dates without completed payments. In these cases, neither the settlement files nor the directories that should have contained settlement files will exist.

info

If a merchant has refunded more money than the sum of payments, so that the balance is negative, we will not create settlement reports. We cover the negative balance for a short while, but if it persists, we will send an invoice to the merchant to settle the balance.

There are no settlement reports for the test environment.

For help finding the reports, see How to get settlement data.

Sparkles

Net and gross settlements​

Net settlement (default): Fees are deducted before the transfer reaches your bank account. What you receive is the payment amount minus Vipps MobilePay fees. This is simpler for accounting — no separate fee invoices to match.

Gross settlement (rare): You receive the full payment amount, and Vipps MobilePay invoices you separately for fees. This is only offered in exceptional cases, as it requires Vipps MobilePay to extend credit to the merchant while fees are outstanding — which involves additional cost, risk, and compliance checks.

For gross settlements, if the merchant's organization number is registered as an EHF recipient, Vipps MobilePay sends invoices as EHF. If not, the invoices are sent by email. To change the invoice recipient, please contact customer service.

See Settlement report availability for information about settlement files when the balance is negative.

Identifying payments​

If you need to use the payment's ID to identify a payment, then use an online solution, such as the ePayment API.

Payment ID

A payment ID can be set by the merchant in the API payment request that is generated by the POS or order system. This is either orderId or reference.

  • orderId (requests made with Recurring API and eCom API)
  • reference (requests made with the ePayment API)

Transaction ID

The transaction ID (transactionID) is set by Vipps MobilePay.

Settlement ID

The settlement ID (settlementID) is set by both the bank and Vipps MobilePay.

How the IDs fit together

Multiple stores per sales unit​

If you have multiple stores per sales unit, prefix the order reference with a unique ID per store. You can search the report data for the unique store ID to find the transaction data per store.

Setup for single MSN for multiple stores: Payment and settlement

Additional info for recurring payments​

For recurring payments, the orderID is an optional field. If orderID is not specified by the merchant when making a charge, the settlement report shows the automatically generated chargeID in the orderID field. If orderID is in use, this is also used in the settlement report.

See the Recurring API for more details.

GDPR​

We need the customer's consent before sharing personal information.

Settlement reports generally don't contain personal information; however, payments made with Vippsnummer and MobilePay-nummer may have personal information and must be treated with care.

See the FAQ: Why are the customer names not shown on the transaction overview?

Last updated on