canonical: https://jentic.com/apis/nets.eu/nets

# Nets API Marketplace

Jentic publishes the only available OpenAPI specification for Nets API Marketplace, keeping it validated and agent-ready. Nets is one of the largest Nordic payment processors, handling card acquiring and account-to-account payments for merchants across Denmark, Norway, Sweden, and Finland. This API exposes payment creation and lookup along with a merchant directory endpoint, suitable for accepting payments and onboarding merchants on the Nets network. Use it for marketplace-style flows where merchants and payments share a single integration surface.

## For AI agents

Create and look up Nets payments and resolve merchant records on the Nets payment network.

## Scope

Does not handle KYC onboarding, dispute management, or payout scheduling - use for Nets payment creation, lookup, and merchant resolution only.

## Capabilities

- Create a new card payment against a merchant on the Nets network
- Look up the status of an existing payment by id
- Resolve merchant directory data for an acquirer-side reconciliation flow
- Confirm settlement state for a payment before fulfilling an order
- Power a marketplace checkout that routes to the correct Nordic merchant

## Use cases

### Nordic Marketplace Checkout

Route checkout transactions on a multi-merchant marketplace to the correct Nets merchant account, then track payment status from authorisation through settlement. The combined merchant lookup and payment endpoints give a marketplace operator one integration surface for both directory and money movement on Nets.

Example prompt: Look up merchant MERCH-77 via /merchants, then POST a payment for 250 DKK to /payments tagged with that merchant, and return the payment id.

### Order Fulfilment Gating on Settlement

Before an order is shipped, confirm the corresponding Nets payment has authorised and is moving toward settlement. The GET `/payments/{id}` endpoint exposes the current state so order management systems gate fulfilment on a confirmed authorisation rather than only the customer-side checkout response.

Example prompt: Fetch `/payments/PAY-555` and only mark order ORD-42 as ready-to-ship if status is 'authorised' or 'settled'.

### AI Agent Payment Lookup

Let a customer support agent (human or AI) ask 'what's the state of payment PAY-X?' and have Jentic call the Nets API to return the answer. Removes the need for support staff to log into the Nets portal for routine status checks.

Example prompt: Given the question 'is payment PAY-555 settled?', call `/payments/PAY-555` and return a one-line status summary.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/payments` | Create a new payment |
| GET | `/payments/{id}` | Get a payment by id |
| GET | `/merchants` | List merchants on the Nets network |

## Key resources

- **Payments** — Create and look up Nets payments by id
- **Merchants** — Resolve merchants on the Nets marketplace network

## Why Jentic

- **Setup:** Wiring the Nets API Marketplace by hand means setting its Authorization API key header, targeting the api.nets.eu host, and shaping payment creation and merchant lookup calls yourself. Through Jentic you install once, import Nets from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Nets creates payments from the request body, so limit the agent to the operations it needs, such as creating a payment or looking one up by id, and leave out the ones it should not run.
- **Credential handling:** Your Nets 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 'create a Nets payment' or 'resolve a merchant', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Adyen Checkout API** — Adyen is a global card acquirer with broad coverage including the Nordics; richer feature set than Nets' marketplace surface.
- **Stripe API** — Stripe offers card acquiring and marketplace flows globally with extensive developer tooling.
- **PayPal Orders API** — PayPal complements card payments on Nets with a wallet alternative checkout option.

## FAQ

### Why is there no official OpenAPI spec for the Nets API?

Nets does not publish a single consolidated OpenAPI specification across its marketplace endpoints. Jentic generates and maintains this spec so that AI agents and developers can call Nets API Marketplace via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Nets API use?

The Nets API uses API key authentication. Your key is provisioned by Nets when you onboard as a merchant or partner and is passed as a request header. Through Jentic the key is stored encrypted in the vault and never exposed to the agent context.

### Can I create a payment with the Nets API?

Yes. POST /payments accepts an amount, currency, and merchant reference and returns a payment id you can later look up via GET `/payments/{id}.` Use it as the server-side leg of a Nordic checkout.

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

Nets does not publish a public rate limit on this endpoint set; throughput is bounded by your acquiring contract. For high-volume merchants, confirm peak limits with your Nets account manager.

### How do I look up merchants on the Nets network through Jentic?

Run jentic.search('list nets merchants'), load the matching operation, and execute GET /merchants. Jentic returns the merchant list which can be filtered client-side or used to route a marketplace payment.

### Does the Nets API support refunds and captures?

This OpenAPI surface focuses on payment creation, lookup, and merchant resolution. Refund and capture flows live in Nets' broader ecosystem (Easy, Netaxept) - call your Nets account manager to confirm which surface fits your use case.

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

Yes. Because Jentic One runs self-hosted on your own infrastructure, your own rules decide which Nets operations and credentials the agent may use. You can allow it to look up a payment by id (GET `/payments/{id}`) or resolve merchants (GET /merchants) while withholding payment creation (POST /payments), or grant only the operations a given workflow needs. The agent can call nothing you have not explicitly permitted, and your Nets API key is injected at execution time rather than exposed to the agent.