canonical: https://jentic.com/apis/resurs.com/resurs

# Resurs Bank Merchant API

Resurs Bank Merchant API for e-commerce payment processing. Supports payment creation, management, and store configuration with OAuth 2.0 authentication. The API exposes 8 endpoints secured with bearer authentication.

## For AI agents

Programmatically obtain an oauth 2.0 access token, get available stores. Covers 8 operations with bearer authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Obtain an OAuth 2.0 access token
- Get available stores
- Create a new payment
- Capture an authorized payment
- Cancel an authorized payment

## Use cases

### Payments Operations

Use the Resurs Bank Merchant API to perform payments operations programmatically. The API provides 8 endpoints covering core functionality including obtain an oauth 2.0 access token, get available stores, get available payment methods for a store.

Example prompt: Call POST `/oauth2/token` to obtain an oauth 2.0 access token

### Automated Oauth2 Management

Automate oauth2 operations by combining multiple Resurs Bank Merchant API endpoints. Agents can get available stores and then get available payment methods for a store in a single workflow.

Example prompt: Call GET `/v2/stores` to get available stores, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Resurs Bank Merchant API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'obtain an oauth 2.0 access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/oauth2/token` | Obtain an OAuth 2.0 access token |
| GET | `/v2/stores` | Get available stores |
| POST | `/v2/stores/{storeId}/payment_methods` | Get available payment methods for a store |
| POST | `/v2/payments` | Create a new payment |
| GET | `/v2/payments/{paymentId}` | Get payment details |
| POST | `/v2/payments/{paymentId}/capture` | Capture an authorized payment |
| POST | `/v2/payments/{paymentId}/cancel` | Cancel an authorized payment |
| POST | `/v2/payments/{paymentId}/refund` | Refund a captured payment |

## Key resources

- **Oauth2** — Operations for oauth2
- **Payments** — Operations for payments
- **Stores** — Operations for stores

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/resurs.com/resurs/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Resurs Bank Merchant API by hand means running the OAuth 2.0 client_credentials grant for a bearer token, choosing the production or integration merchant-api.resurs.com host, and managing payment lifecycle calls yourself. Through Jentic you install once, import Resurs Bank Merchant API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Resurs Bank Merchant API puts the payment id in the URL path (`/v2/payments/{paymentId}/...`), so a rule can pin your agent to one payment: it can read and capture that payment and nothing else. You choose the operations it may call, so actions like cancellation or refund are not included unless you add them.
- **Credential handling:** Your Resurs Bank Merchant API credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a payment' or 'capture a payment', and Jentic returns the matching Resurs Bank Merchant API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Resurs Bank Merchant API use?

The Resurs Bank Merchant API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I obtain an oauth 2.0 access token with the Resurs Bank Merchant API?

Yes. Use the POST `/oauth2/token` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Resurs Bank Merchant API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I obtain an oauth 2.0 access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'obtain an oauth 2.0 access token'. Jentic returns the matching Resurs Bank Merchant API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Resurs Bank Merchant API have?

The Resurs Bank Merchant API exposes 8 endpoints covering oauth2, payments, stores operations.

### Can I limit what my agent is allowed to do with the Resurs Bank Merchant API?

Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials the agent may use. Because the Resurs Bank Merchant API puts the payment id in the URL path, such as `/v2/payments/{paymentId}/capture`, you can pin the agent to a single payment and allow only reading and capturing it. You choose the operations it may call, so sensitive actions like cancel or refund stay off limits unless you explicitly grant them.