MobilePay API

Name: MobilePay API API
Brand: MobilePay API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey3 EndpointsREST

For Agents

Initiate MobilePay mobile payments in Denmark, retrieve payment status, and issue refunds through three API key-authenticated endpoints.

Connect the MobilePay API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MobilePay API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MobilePay API API.

Initiate a MobilePay payment for a Danish customer

Retrieve the status of a specific payment by its ID

Issue a refund against a completed MobilePay payment

Use Cases

Patterns agents use MobilePay API API for, with concrete tasks.

GET STARTED

Start building with MobilePay API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for MobilePay API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for MobilePay API, keeping it validated and agent-ready. The MobilePay API hosted at api.mobeco.dk exposes mobile payment endpoints for the Danish MobilePay product. The three endpoints cover creating a new payment, fetching the current status of a specific payment by ID, and issuing a refund. Authentication uses an API key passed in the Authorization header.

★ E-Commerce Checkout in Denmark

A Danish e-commerce checkout offers MobilePay alongside card payments because of its dominance in the Danish consumer market. The merchant creates a payment via POST /payments with the order amount and customer reference, then redirects the user to confirm in the MobilePay app. After confirmation the merchant polls the payment status endpoint to release the order for fulfilment.

Create a payment for 249.00 DKK via POST /payments, capture the returned payment ID, and poll GET /payments/{id} until status is completed

Order Refund Workflow

When a Danish customer returns a purchase, customer service issues a refund through the refunds endpoint referencing the original payment ID and the refund amount. Partial refunds for partial returns are supported. The refunded amount is returned to the customer's MobilePay app and reconciled against the original transaction in the merchant ledger.

Issue a refund for the original payment by calling POST /refunds with the payment ID and refund amount in DKK

Payment Status Reconciliation

A finance team reconciles MobilePay payments against orders by polling the GET /payments/{id} endpoint for any orders that have not received a webhook confirmation. The structured status response — pending, completed, cancelled, failed — drives the reconciliation script to release, retry, or mark the order as unpaid.

For each unconfirmed order ID, call GET /payments/{id} and update the order status based on the returned payment state

Agent-Driven Payment Flow

An agent discovered through Jentic creates the MobilePay payment, monitors its status, and triggers refunds when ordered. Jentic stores the API key in its credential vault so the agent only invokes the create, lookup, and refund operations rather than holding the raw Authorization header value in its runtime.

Use Jentic to find the MobilePay create payment operation and execute it with order amount 199.00 DKK and customer reference {orderId}

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for mobilepay api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/payments

Create a new MobilePay payment

GET

/payments/{id}

Retrieve a payment by ID

POST

/refunds

Issue a refund against a payment

POST

/payments

Create a new MobilePay payment

GET

/payments/{id}

Retrieve a payment by ID

POST

/refunds

Issue a refund against a payment

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

MobilePay API keys are stored encrypted in the Jentic vault. Agents call create payment, status, and refund operations through Jentic and the Authorization header is injected at request time, so the raw key never enters agent context.

Intent-based discovery

Agents search Jentic with intents like create mobilepay payment or refund mobilepay and Jentic returns the matching Mobeco operation with input schema and example payload.

Time to first call

Direct MobilePay integration: 1-2 days to handle auth, status polling, and refunds. Through Jentic: under 1 hour to search, load, and execute the create payment operation.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

MobilePay (mobilepay.dk) API

Alternative MobilePay API surface in the corpus

Use this when the integration partner specifies the mobilepay.dk endpoints rather than Mobeco's gateway.

Alternative

Stripe API

Global card and wallet payments platform

Choose Stripe when the merchant needs broad international card and wallet support beyond Danish MobilePay.

Complementary

Mollie API

European payments aggregator with multiple local methods

Use alongside MobilePay when the checkout also needs iDEAL, Bancontact, or other European local methods.

FAQs

Specific to using MobilePay API API through Jentic.

Why is there no official OpenAPI spec for MobilePay API?

Mobeco does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MobilePay API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the MobilePay API use?

The API uses an API key passed in the Authorization header. Generate the key from the Mobeco merchant portal and include it on every request. Through Jentic the key is stored in the credential vault and injected at execution time so agent code never sees the raw value.

Can I issue partial refunds with the MobilePay API?

Yes. POST /refunds takes the original payment ID and a refund amount that may be smaller than the original charge. The refund is returned to the customer's MobilePay account and reconciled against the original payment.

What are the rate limits for the MobilePay API?

Mobeco applies per-merchant rate limits on payment creation and refund issuance to protect against abuse. Status lookups have higher quotas than write calls. Coordinate with Mobeco support for current numeric limits before high-volume promotions.

How do I create a payment through Jentic?

Search Jentic for create mobilepay payment, load the schema for POST /payments, and execute with the order amount in DKK and a merchant order reference. The response includes the payment ID and a status to poll.

Does the MobilePay API cover other Nordic countries?

This API surface targets the Danish MobilePay product. For Norwegian, Finnish, or other Nordic mobile-payment products, use the country-specific API for that market rather than the Mobeco endpoints.