canonical: https://jentic.com/apis/mobilepay.dk/mobilepay

# Mobilepay Dk MobilePay API

MobilePay is a Danish mobile payment solution widely used across Denmark and the Nordics for peer-to-peer transfers and merchant payments. The API exposes a small surface for token exchange and resource lookup, intended for partners and merchants integrating MobilePay into their checkout or customer flows. Authentication is handled via an X-API-Key header and a token endpoint that issues bearer tokens for downstream calls.

## For AI agents

Authenticate against MobilePay and look up MobilePay resources by ID for Danish mobile payment integrations.

## Scope

Does not handle card processing, refunds, or PoS terminals - use for MobilePay token exchange and resource lookup only.

## Capabilities

- Exchange API key credentials for a MobilePay bearer token via the `/auth/token` endpoint
- Retrieve the list of MobilePay resources available to the authenticated merchant
- Fetch a specific MobilePay resource by its identifier
- Authorise downstream MobilePay calls with X-API-Key header credentials
- Bridge MobilePay merchant accounts into checkout and back-office systems

## Use cases

### Danish merchant onboarding

Merchants integrating MobilePay into a Danish online checkout use the `/auth/token` endpoint to exchange their issued API key for a short-lived bearer token, then call /resources to discover the merchant resources available to that key. This pattern keeps long-lived credentials out of runtime traffic and aligns with MobilePay's partner integration model for the Danish market.

Example prompt: Call POST `/auth/token` with the merchant's X-API-Key, then GET /resources and return the list of resource IDs available to that account.

### Resource lookup for reconciliation

Back-office and reconciliation tools fetch a single MobilePay resource by ID using GET `/resources/{id}` to verify the resource exists and pull its current attributes. This supports lightweight reconciliation between MobilePay-linked merchant data and an internal ledger or CRM record, without paginating the full resource list.

Example prompt: Call GET `/resources/{id}` for resource ID 'res_123' and return whether the resource was found along with its attributes.

### Agent-driven MobilePay integration via Jentic

An AI agent that needs to wire a Danish merchant into MobilePay can search Jentic for 'authenticate to MobilePay', load the `/auth/token` operation schema, and execute the call without ever holding the raw API key. The agent then chains into /resources to discover what the credential can access, all from within a single intent-driven workflow.

Example prompt: Search Jentic for 'authenticate to MobilePay', load the `/auth/token` schema, execute the token exchange, then call /resources and report the discovered resource IDs.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/token` | Exchange API key for a bearer token |
| GET | `/resources` | List MobilePay resources |
| GET | `/resources/{id}` | Retrieve a MobilePay resource by ID |

## Key resources

- **Authentication** — Token exchange endpoint that accepts an API key and returns a bearer token
- **Resources** — List and retrieve the MobilePay resources available to the authenticated merchant

## Why Jentic

- **Setup:** Wiring this MobilePay API by hand means handling its X-API-Key auth, running the token exchange at `/auth/token`, and threading the token into resource lookups yourself. Through Jentic you install once, import the MobilePay API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** This MobilePay API puts the resource id in the URL path (`/resources/{id}`), so a rule can pin your agent to reading one resource: it can exchange a token and look up that resource. You choose the operations it may call, so nothing beyond token exchange and resource reads is included unless you add it.
- **Credential handling:** Your MobilePay API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'exchange a MobilePay token' or 'look up a resource', and Jentic returns the matching MobilePay operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe API** — Global card and wallet payment processor with broader coverage outside the Nordics
- **Mollie API** — European payments API covering iDEAL, SEPA, cards and other local methods
- **Revolut Merchant API** — Merchant payments and payouts API used alongside Nordic wallets

## FAQ

### What authentication does the MobilePay API use?

The MobilePay API uses an apiKey scheme: callers send their key in the X-API-Key request header and exchange it for a bearer token at POST `/auth/token.` Through Jentic, the X-API-Key value is held in your Jentic One instance and never exposed to the agent's context.

### Can I list all MobilePay resources for my merchant account?

Yes. Call GET /resources with a valid bearer token to retrieve the resources tied to the authenticated merchant. Use GET `/resources/{id}` to fetch a single resource by its identifier.

### What are the rate limits for the MobilePay API?

Rate limits are not declared in the OpenAPI specification. Refer to the MobilePay developer portal at https://developer.mobilepay.dk/ for the current per-merchant quotas and back off on HTTP 429 responses.

### How do I authenticate to MobilePay through Jentic?

Install the SDK with pip install jentic, then search for 'authenticate to MobilePay', load the `/auth/token` operation schema, and execute it. Jentic injects the X-API-Key from the vault and returns the bearer token to the agent.

### Does the MobilePay API support payment capture or refunds?

The OpenAPI specification published in this catalogue covers token exchange and resource lookup only. For payment capture, refunds, or PoS integrations, consult the MobilePay developer portal for the relevant product API.

### Is the MobilePay API free to use?

MobilePay is a commercial payments platform: API access is gated by merchant agreements and partner onboarding. There is no public free tier. Get started with Jentic One, the self-hosted execution layer.

### Can I limit what my agent is allowed to do with the MobilePay API?

Yes. Jentic One runs self-hosted, so your own rules decide which MobilePay operations and credentials the agent may use. Because the resource id sits in the URL path at GET `/resources/{id}`, you can pin the agent to token exchange at POST `/auth/token` and reading a single resource, leaving GET /resources and everything else off unless you add it. Only the operations you allow are callable.