Computop API

Name: Computop API API
Brand: Computop API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey3 EndpointsREST

For Agents

Create payments, retrieve payment status, and issue refunds through Computop's payment service for Swish and related methods.

Quickstart

Get started with Computop API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a Computop payment and check its status"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Computop API API.

Create a payment for a checkout transaction through Computop

Retrieve the status and details of an existing payment by id

Issue a refund against a settled payment

Route Swish and supported alternative payment methods through a single endpoint

Track payment lifecycle from creation through refund for reconciliation

GET STARTED

Start building with Computop API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Computop API, keeping it validated and agent-ready. Computop is a European payment service provider, and this API surface covers payment creation, payment retrieval, and refunds for Swish and other payment methods routed through Computop. It is intended for merchants who already have a Computop merchant account and need a programmatic integration for new charges and refund processing rather than the full Computop Paygate gateway suite.

Use Cases

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

★ Swish Checkout for Nordic Merchants

Accept Swish payments at checkout for merchants selling into Sweden. POST /payments creates the Swish payment, and GET /payments/{id} polls for its status until it reaches an authorized or settled state. Nordic e-commerce merchants integrate this when their broader processing already runs through Computop and they want a single API to add Swish.

Create a payment for SEK 499.00 via Swish for order id A-7711 and poll /payments/{id} every 2 seconds until status is settled or 60 seconds elapse

Refund Processing

Issue a refund against a previously settled Computop payment when a customer returns goods or cancels a service. POST /refunds creates the refund record referencing the original payment id and the amount. Operations and customer-service teams use this to handle returns without logging into the Computop merchant portal.

Issue a refund of EUR 25.00 against payment id pmt_88421 with reason 'customer requested return'

Reconciliation and Status Auditing

Reconcile internal order records against Computop payments by retrieving each payment's current state. GET /payments/{id} returns the status, amount, and metadata for a payment so finance teams can match settled transactions to invoices and flag pending or failed ones. This is the simplest reconciliation surface for teams not yet using the full Computop reporting feed.

For each order id in the open invoices list, fetch its associated Computop payment via GET /payments/{id} and report any with status not equal to settled

Agent-Driven Payment Operations via Jentic

Let an AI assistant handle ad-hoc payment and refund tasks for support agents working in chat. Through Jentic the assistant searches by intent, loads the schema for the relevant Computop operation, and executes the call without the developer wiring auth or polling. This collapses what would normally be a portal-driven manual task into a single chat command.

On the prompt 'refund order A-7711 in full', look up its payment id, fetch the original amount, and issue a refund for that amount via POST /refunds

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/payments

Create a payment

GET

/payments/{id}

Retrieve a payment by id

POST

/refunds

Issue a refund against a payment

POST

/payments

Create a 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

Computop API keys are stored encrypted in the Jentic vault and injected as the Authorization header at execution time. The raw key never enters the model context or application logs.

Intent-based discovery

Agents search Jentic with intents like 'create a Computop payment' and Jentic returns the matching operation with its parameter schema, so the agent can call POST /payments without browsing developer docs.

Time to first call

Direct integration: 1-2 days for auth, payment creation, status polling, and refund handling. Through Jentic: under 1 hour via search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Global payment platform with broad coverage of cards, wallets, and local methods

Choose Stripe when you need broad global coverage and a richer SDK; choose Computop when your acquiring contract is with Computop or you need direct Swish acceptance.

Alternative

Adyen Account Service

Adyen's platform APIs covering global card and local-method acquiring

Choose Adyen when your business needs an acquirer with global reach and platform-payments features beyond Computop's regional focus.

Alternative

Braintree

PayPal-owned payment processor with cards, PayPal, and digital wallets

Choose Braintree when you want native PayPal acceptance alongside cards rather than Computop's European local-method focus.

FAQs

Specific to using Computop API API through Jentic.

Why is there no official OpenAPI spec for Computop API?

Computop does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Computop 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 Computop API use?

The API uses an API key passed in the Authorization request header. Through Jentic the key is stored encrypted in the vault and injected at execution time, so the raw key never enters the agent's prompt or logs.

Can I issue a refund with the Computop API?

Yes. Call POST /refunds with the original payment id and the refund amount. Partial refunds are supported by passing an amount lower than the original payment value, and the refund record is returned with its own id for tracking.

What are the rate limits for the Computop API?

Computop applies merchant-specific rate limits negotiated as part of the merchant contract; there is no published global limit. Agents should add backoff on HTTP 429 responses; Jentic surfaces these as structured errors rather than retrying silently.

How do I create a Swish payment through Jentic?

Run the Jentic search query 'create a Computop Swish payment', load the returned operation (POST /payments), and execute it with the amount, currency, and method set to Swish. Then poll GET /payments/{id} until the status reaches authorized or settled.

Is this API the same as Computop Paygate?

No. This API is the modern REST surface focused on payment creation, retrieval, and refunds. The legacy Computop Paygate uses a different, form-based protocol. Use this REST API for new integrations and keep Paygate for existing merchant flows already wired against it.