Nexi Group API
✓ Official Vendor SpecPaymentsPayment ProcessingapiKey3 EndpointsREST
For Agents
Create checkout sessions and process card or Swish payments through the Nexi Group Nordic API. Three endpoints cover session creation, payment, and payment status lookup.
Use for: Create a checkout session for a Nordic e-commerce purchase, Process a Swish mobile payment for 199 SEK, Get the status of an existing payment by ID, Set up a checkout session with a return URL after payment
Not supported: Does not handle refunds, captures, pay-by-link, or merchant onboarding — use for Nordic checkout session creation, payment processing, and payment status lookup only.
Nexi Group is the parent payments company that operates across the Nordics under brands such as Nets and Bambora. This API surface covers Swish checkout — the Nordic mobile payment scheme — and standard card payment processing through three endpoints: create a checkout session, process a payment, and retrieve a payment by ID. Authentication uses an API key passed in the Authorization header. The base host api.nexigroup.com is distinct from the Italian xpay.nexigroup.com gateway covered by the separate Nexi XPay spec.
Install Jentic One Beta
Connect the Nexi Group API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Nexi Group 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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: 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 | sh2
Step 2: 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 instanceJentic 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 Nexi Group API.
Create a checkout session with POST /checkout/sessions for embedded or redirected payment flows
Process a card or Swish payment through POST /payments with the chosen payment method
Retrieve the current status of a payment by ID via GET /payments/{id}
Authenticate requests with an API key passed in the Authorization header
Reach the Nordic Swish mobile payment scheme without integrating directly with each Swedish bank
Use Cases
Patterns agents use Nexi Group API for, with concrete tasks.
★ Nordic E-Commerce Checkout
Nordic merchants accept Swish, card, and other regional payment methods by calling POST /checkout/sessions to create a session keyed to the cart, then redirecting the shopper to the returned URL. Once the shopper completes payment, the merchant calls GET /payments/{id} to confirm the captured amount before releasing the order. This is the standard pattern for any merchant whose acquiring relationship sits with Nexi Group.
Create a checkout session for 499 SEK with a return URL pointing back to the merchant's order page
Swish Mobile Payments
Swedish merchants accept Swish — Sweden's bank-backed mobile payment scheme — through Nexi Group rather than building direct integrations with each bank. POST /payments with the Swish payment method initiates the request, and the shopper approves it in the Swish app on their phone. GET /payments/{id} polls the result so the merchant knows when the funds have been authorised.
Initiate a Swish payment for 250 SEK from a customer's phone number and poll GET /payments/{id} until the status is final
Status Polling for Order Fulfilment
Order management systems rely on GET /payments/{id} to confirm payment status before fulfilment. Because Swish and other asynchronous payment methods do not return a final result on the create call, the OMS calls the status endpoint with backoff until it receives a settled or failed state. Only then does the system trigger picking, packing, or digital delivery.
For payment id pay_456, poll GET /payments/{id} every 5 seconds for up to 60 seconds and report the final status
Agent-Managed Payment Confirmation
An AI agent uses Nexi Group through Jentic to confirm payment status when a downstream event — a customer asking 'did my payment go through?' — needs an authoritative answer. The agent calls GET /payments/{id} with the merchant's reference, parses the response, and returns a clear confirmation or failure reason. Jentic supplies the API key in the Authorization header automatically.
When a customer asks about payment status, look up the payment by id and reply with a one-sentence confirmation or failure reason
Key Endpoints
3 endpoints — nexi group is the parent payments company that operates across the nordics under brands such as nets and bambora.
METHOD
PATH
DESCRIPTION
POST
/checkout/sessions
Create a checkout session for redirect or embedded flow
POST
/payments
Process a card or Swish payment
GET
/payments/{id}
Retrieve a payment's current status
POST
/checkout/sessions
Create a checkout session for redirect or embedded flow
POST
/payments
Process a card or Swish payment
GET
/payments/{id}
Retrieve a payment's current status
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Nexi Group API keys are stored encrypted in the Jentic vault and injected into the Authorization header at request time. Because the same key authorises live payment captures, keeping it out of the agent's context and chat history is non-negotiable.
Intent-based discovery
Agents search Jentic for intents like 'create a Nordic checkout session' or 'get a payment status' and Jentic returns the matching POST /checkout/sessions or GET /payments/{id} operation with its schema, so the agent picks the right endpoint without reading the docs.
Time to first call
Direct integration: 2-3 days to wire the Authorization header, build the checkout session and Swish polling flow, and test against the sandbox. Through Jentic: under 30 minutes — search, load schema, execute, with the polling logic still owned by the agent.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe API
Stripe is a global payment processor that also supports Swish through PaymentIntents
Choose Stripe for global coverage and a single processor across multiple countries. Choose Nexi Group when the merchant has a Nordic acquiring relationship with Nexi or wants direct Swish settlement through Nexi.
FAQs
Specific to using Nexi Group API through Jentic.
What authentication does the Nexi Group API use?
The Nexi Group API uses an API key sent in the Authorization header on every request. Through Jentic the key is held in the encrypted vault and Jentic injects it on each call, so the merchant credential never appears in the agent's prompt or log output.
Can I accept Swish payments with the Nexi Group API?
Yes. POST /payments accepts Swish as a payment method, and the shopper approves the request in the Swish mobile app. Because Swish is asynchronous, the calling code must poll GET /payments/{id} to confirm the final state before fulfilling the order.
How is the Nexi Group API different from Nexi XPay?
Nexi Group's api.nexigroup.com host covers the Nordic checkout flow with three endpoints — checkout session, payment, and payment status. Nexi XPay (xpay.nexigroup.com) is the Italian gateway with 16 endpoints including hosted payment pages, pay-by-link, refunds, and captures. Choose the API that matches the merchant's acquiring relationship.
How do I confirm a payment status through Jentic?
Search Jentic for 'get the status of a nexi group payment', load the GET /payments/{id} schema, and execute with the payment id. Jentic injects the Authorization header automatically and returns the structured payment record.
What currencies does the Nexi Group API support?
The Nordic surface covers SEK, NOK, DKK, and EUR for the markets where Nexi Group operates. The exact set available to a merchant depends on the acquiring contract; the spec accepts any ISO currency code in the request payload, but settlement is constrained by the merchant configuration on Nexi's side.
GET STARTED