Vipps MobilePay for GoHighLevel v1.0

Accept payments on GoHighLevel using Vipps MobilePay — the dominant mobile payment platform across the Nordics. Covers Norway, Denmark, and Finland — used by 11 million customers across 330,000+ merchants.

Overview

This integration connects your GoHighLevel sub-accounts to Vipps MobilePay, letting you accept online payments directly inside GHL — for one-time charges, subscriptions, free trials, and saved-card flows.

Once installed, every GHL location can configure its own Vipps MobilePay test and live API credentials. Customers see a branded checkout in your funnels, order forms, calendar bookings, and invoices.

What's included

Installation

Configuration

Test vs Live mode

Each location supports both modes simultaneously. Test mode uses Vipps's sandbox at apitest.vipps.no — no real money moves. You'll need to install the MT (Merchant Test) app from TestFlight / Google Play to simulate the customer side. Switch to live once your Vipps sales unit is approved.

Currencies by country

Test sales units inherit the country code of the merchant — a Norwegian merchant cannot create payments in DKK, etc.

Payment methods

Customers tap "Pay with Vipps" and either confirm in their phone's Vipps/MobilePay app (mobile) or get a landing page with a QR code (desktop). Visa/Mastercard card fallback is available for customers without the app.

Vipps & MobilePay apps

The Vipps (Norway) and MobilePay (Denmark, Finland) apps are the primary payment surface for customers — over 80% of Danes and ~75% of Norwegians have them installed.

• Push message flow: when the customer's phone number is known, Vipps can send a push notification directly to their app for one-tap approval.
• Landing page flow: for desktop / unknown phone, Vipps shows a hosted page with a QR code the customer scans with their phone.
• Card fallback: Vipps's hosted checkout also accepts Visa/Mastercard for customers who don't have the app.

Subscriptions

Create recurring subscriptions in GHL — daily, weekly, monthly, yearly, or custom intervals. The customer's card is securely saved on the first charge and reused for renewals automatically.

• Renewals run automatically on the scheduled date.
• Failed renewals are retried per GHL's dunning settings.
• Customers and admins can cancel anytime from the GHL UI.

Free trials

Supported. When GHL activates a 0 NOK trial subscription, the integration records the trial without charging. When the trial period ends, GHL automatically triggers the first real charge against the saved card.

The customer must enter a valid card during trial signup so renewals can succeed. Cards added during trial are validated when the first real charge runs.

Saved cards (card-on-file)

Once a customer pays, their card is tokenized by Vipps MobilePay and saved to their GHL contact. Future charges (subscription renewals, one-click checkouts) use the stored token — no card re-entry needed.

Cards can be listed and managed per contact via GHL's payment methods UI.

Refunds

Issue refunds from GHL → Payments → Transactions. Both full and partial refunds are supported. The refund is processed instantly against Vipps MobilePay; the customer's bank usually returns funds within 5–10 business days.

Test environment

Vipps's test environment uses the MT (Merchant Test) app on your phone instead of test cards. You'll get test user credentials (phone number + national ID) auto-generated when you create your sales unit on the portal.

1. Sign up on portal.vippsmobilepay.com and create a test sales unit
2. Install the MT app from TestFlight (iOS) or Google Play (Android)
3. Log in to MT with the auto-generated test phone number from your portal
4. Test payments will trigger a push notification to MT instead of the real Vipps app

Full guide: Vipps test environment docs

Webhooks Developer

The integration listens for Vipps ePayment webhook events and forwards relevant updates to GHL:

• epayments.payment.created.v1 — payment initiated
• epayments.payment.authorized.v1 — customer approved in app
• epayments.payment.captured.v1 — funds captured
• epayments.payment.refunded.v1 — refund completed
• epayments.payment.aborted.v1 / epayments.payment.expired.v1 / epayments.payment.terminated.v1 — failure variants

Webhook endpoint:

POST https://vipps.leadconnectorpay.com/webhooks/vipps

Signature verification uses your Vipps MobilePay webhook secret (returned when you register the webhook via the Vipps Webhooks API). Manage webhooks through the Vipps Webhooks API as described in the Vipps developer docs.

Troubleshooting

"Pay with Vipps" button doesn't show

• Confirm your sales unit's credentials (Client ID, Client Secret, Subscription Key, MSN) are saved correctly for the active mode (test vs live).
• Check that your sales unit is approved for the mode you're using — live charges require an approved live sales unit.
• Verify the customer's country matches your sales unit's country (a Norwegian sales unit can only charge in NOK, etc.).

Payment fails with a minimum-amount error

Vipps MobilePay rejects charges below its minimum amount. Free trials (0 NOK) are handled separately — the integration won't reject them.

Live currency charge fails

Each sales unit is tied to a single country and currency (NOK, DKK, or EUR). Make sure the charge currency matches your sales unit's country, and that the sales unit is approved for live.

Subscription renewal fails

• Verify the customer's saved card hasn't expired.
• Check GHL's dunning settings — failed renewals retry on a schedule.
• If the card is declined, GHL notifies the customer to update payment info.

FAQ

Which customers can pay?

Customers with the Vipps app (Norway) or MobilePay app (Denmark, Finland) get the one-tap wallet flow. Customers without the app can still pay with Visa/Mastercard via the hosted card fallback.

What fees does Vipps MobilePay charge?

Pricing is set by Vipps MobilePay — see vippsmobilepay.com/priser. Rates differ by country and payment method.

Can I use one Vipps MobilePay sales unit for multiple GHL locations?

Yes — but each location should configure its own credentials. The integration scopes credentials per location.

Are payments PCI compliant?

Yes. Card details are entered on Vipps MobilePay's hosted checkout and never reach your servers. The integration only handles tokens, never raw card data.

Does it support strong customer authentication (SCA / 3D Secure)?

Yes, automatically. Vipps MobilePay handles authentication in the app or via redirect; the integration handles the return-flow and finalizes the payment.

Support

• 📧 Email: support@leadconnectorpay.com
• 📚 Vipps MobilePay docs: developer.vippsmobilepay.com
• 🆘 GHL marketplace: open a support ticket from the app listing