Merchantsafeunipay Payten MSU API

Name: Payten MSU API
Brand: Payten MSU API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey20 EndpointsREST

For Agents

Process card payments, manage saved cards, issue refunds, and generate pay-by-link URLs through the Payten MSU gateway.

Install Jentic One Beta

Connect the Payten MSU API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Payten MSU 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.

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 | sh

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 instance

Jentic 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 Payten MSU API.

Authenticate merchants with session tokens and refresh or kill sessions during long-running operations

Process card sales and pre-authorisations, then capture or void the held amount

Issue full or partial refunds against a prior MSU transaction

GET STARTED

Start building with Payten MSU API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Payten MSU API, keeping it validated and agent-ready. MerchantSafeUnipay (Payten) is a payment gateway widely used across Turkey and South-Eastern Europe for card-not-present transactions, recurring billing, and saved-card commerce. The v2 API covers session management, sale and pre-authorisation flows, voids and refunds, saved-card vault operations, and pay-by-link generation, exposing the merchant operations needed to run an end-to-end checkout from a single integration.

Use Cases

Patterns agents use Payten MSU API for, with concrete tasks.

★ Card-Not-Present Checkout

E-commerce merchants in Turkey and the wider region can route checkout charges through Payten MSU using POST /sale for direct sales or POST /preauth followed by POST /postauth when funds need to be held before capture. The API also handles voids and refunds, so the full checkout lifecycle sits behind a single gateway integration.

Call POST /session to obtain a session token, then POST /sale with amount 199.90 TRY and the card token to charge a customer.

Saved-Card Recurring Billing

Subscription businesses can vault customer cards via POST /card/add and charge them on a schedule with /sale calls referencing the saved card. POST /card/edit and POST /card/delete keep the vault aligned with customer changes, supporting recurring SaaS, utilities, and instalment use cases.

Call POST /card/add to vault a card, then POST /sale on the next billing date referencing that saved card.

Pay-By-Link Invoicing

Service businesses sending invoices over WhatsApp, SMS, or email can generate hosted payment URLs via POST /payByLink/add and edit or cancel them through /payByLink/edit and /payByLink/cancel. Customers complete the payment on Payten-hosted pages, removing the need to host a checkout for ad hoc sales.

Call POST /payByLink/add with amount 1500 TRY and customer email to create a payment link, then send the URL to the customer.

Reconciliation and Refund Workflows

Finance teams can use POST /query to look up the status of historical transactions and POST /refund to issue refunds against settled charges. Combined with /void for pre-capture cancellations, this supports daily reconciliation, dispute responses, and customer service refund requests.

Call POST /query with the original transaction reference, then POST /refund with the matching amount to refund the customer.

Agent-Built Payment Workflows

An AI agent assembling a checkout, refund, or recurring-billing workflow can discover Payten MSU operations via Jentic's intent search, load the schema for /sale, /refund, or /payByLink/add, and execute the call without writing custom MSU client code or handling raw merchant credentials.

Search Jentic for 'process a card payment with Payten MSU', load the POST /sale schema, and execute the call with session token, amount, and card details.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/session

Create merchant session token

POST

/sale

Process a card sale

POST

/preauth

Pre-authorize a payment

POST

/postauth

Capture a pre-authorized payment

POST

/refund

Refund a transaction

POST

/card/add

Vault a saved card

POST

/payByLink/add

Create a pay-by-link URL

POST

/query

Query historical transactions

POST

/session

Create merchant session token

POST

/sale

Process a card sale

POST

/preauth

Pre-authorize a payment

POST

/postauth

Capture a pre-authorized payment

POST

/refund

Refund a transaction

POST

/card/add

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

MERCHANTUSER and MERCHANTPASSWORD credentials live in the Jentic vault. Agents authenticate to MSU through a scoped Jentic token; raw merchant credentials never enter the agent context.

Intent-based discovery

Agents search Jentic with intents like 'process a card payment' or 'create a pay-by-link', and Jentic returns the matching POST /sale or POST /payByLink/add operation with its request schema.

Time to first call

Direct Payten MSU integration: 3-5 days for session handling, sale and refund flows, vault and pay-by-link, plus reconciliation. Through Jentic: a few hours.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe API

Global card processor with broader currency and method coverage than Payten MSU

Use when the merchant operates outside Turkey or needs Stripe-specific products such as Connect, Billing, or Issuing.

Alternative

Adyen Checkout API

Enterprise unified-commerce gateway covering more regions and acquirers

Use when the merchant needs multi-region acquiring and a single integration across online, in-app, and POS.

Alternative

PayPal Payments API

Wallet-led alternative for cross-border consumer payments

Use when the buyer journey starts from PayPal balance or Pay Later rather than direct card entry.

FAQs

Specific to using Payten MSU API through Jentic.

Why is there no official OpenAPI spec for Payten MSU API?

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

Authentication uses an Authorization header carrying MERCHANTUSER and MERCHANTPASSWORD credentials, exchanged via POST /session for a session token reused on subsequent calls. Through Jentic, the merchant credentials live in the vault and the agent only ever sees a scoped Jentic token.

Can I issue partial refunds with the Payten MSU API?

Yes. POST /refund accepts an amount that can be less than the original transaction total, so partial refunds work the same way as full refunds. Use POST /query first if you need to confirm the original charge is in a refundable state.

What are the rate limits for the Payten MSU API?

The OpenAPI spec does not declare explicit rate limits. Payten enforces gateway-side throttling per merchant and per acquirer; recurring batch jobs should sequence calls and use POST /session/extend to keep a single token alive rather than re-authenticating per request.

How do I generate a pay-by-link through Jentic?

Install the SDK with pip install jentic, search for 'create a Payten pay-by-link', load the POST /payByLink/add operation, and execute it with the amount, currency, and customer details. Jentic returns the hosted URL you can send to the customer.

Does the Payten MSU API support recurring billing?

Yes. Combine POST /card/add to vault the customer card with scheduled POST /sale calls referencing the saved card to charge subscriptions. The Recurring tag groups operations specific to recurring plan configuration.