MONEI API v1

Name: MONEI API v1 API
Brand: MONEI API v1
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey29 EndpointsREST

For Agents

Charge cards, accept Bizum and Apple Pay, manage subscriptions, and issue refunds for merchants on the MONEI gateway. Supports platform-style multi-account routing.

Install Jentic One Beta

Connect the MONEI API v1 to your agent

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

Create one-time card payments and capture or void authorisations on /payments

Process Bizum mobile payments after validating a phone number on /bizum/validate-phone

Manage Apple Pay merchant certificates and verified domains for in-browser checkout

GET STARTED

Start building with MONEI API v1 API

Explore with Jentic

View OpenAPI Document

MONEI is a Spanish payment gateway that lets merchants accept cards, Apple Pay, Google Pay, Bizum, PayPal, and other regional methods through a single integration. The API exposes 29 endpoints covering payment lifecycle (create, confirm, capture, refund, recurring), subscriptions, Apple Pay certificate and domain management, Bizum phone validation, and POS authentication tokens. Multi-account support via the MONEI-Account-ID header lets platforms route transactions on behalf of connected merchants. Rate limiting returns HTTP 429 and all requests must be HTTPS with a User-Agent header.

Use Cases

Patterns agents use MONEI API v1 API for, with concrete tasks.

★ Online Card Checkout for Spanish Merchants

Accept cards and local wallets on a Spanish or European storefront by creating a payment on /payments, redirecting the shopper to MONEI's hosted payment page, and confirming the result via webhook. The 29-endpoint API covers authorisation, capture, void, and refund without the merchant touching card data, satisfying PSD2 SCA requirements through the gateway.

Create a MONEI payment for 49.99 EUR with order id ORD-1042 and return the payment URL the customer should be redirected to.

Bizum Mobile Payments

Bizum is the dominant Spanish peer-to-business mobile payment scheme. With MONEI an agent can validate a customer's phone number on /bizum/validate-phone, create a payment with Bizum as the chosen method, and read the final status. This unlocks an additional 25 million Spanish users without negotiating a separate Bizum acquirer.

Validate the Bizum phone number +34600123456 and create a 12.50 EUR Bizum payment if the number is registered.

Recurring Billing for SaaS

MONEI subscriptions let merchants store a card on file and charge on a schedule via /subscriptions. The API supports pause, resume, plan changes, and cancellation, with each cycle producing a child payment that can be reconciled against accounting. Useful for European SaaS that need EUR-native billing without USD conversion.

Create a monthly 19.99 EUR subscription for customer cus_77 starting on the next billing date and confirm the first charge succeeded.

Apple Pay on the Web

Apple Pay on the web requires both a merchant identity certificate and a list of verified domains. MONEI exposes /apple-pay/certificates and /apple-pay/domains so an agent can provision and rotate certificates and register checkout domains programmatically. This removes a manual step from launching new branded storefronts on the gateway.

AI Agent Payment Operations

An autonomous commerce agent uses Jentic to discover MONEI's payment, refund and subscription endpoints, loads their JSON Schemas, and executes calls without touching raw API keys. The Authorization header and MONEI-Account-ID are injected from the Jentic vault, so the same agent can operate across many merchant accounts on a platform without storing per-merchant secrets in its own context.

Search Jentic for 'process a card payment', load the MONEI create-payment schema, and execute a 25 EUR charge for account acc_123.

Key Endpoints

29 endpoints — monei is a spanish payment gateway that lets merchants accept cards, apple pay, google pay, bizum, paypal, and other regional methods through a single integration.

METHOD

PATH

DESCRIPTION

POST

/payments

Create a payment

GET

/payments/{id}

Retrieve a payment

POST

/payments/{id}/refund

Refund a payment

POST

/subscriptions

Create a subscription

POST

/bizum/validate-phone

Validate a Bizum phone number

POST

/apple-pay/domains

GET

/payment-methods

List enabled payment methods

POST

/payments

Create a payment

GET

/payments/{id}

Retrieve a payment

POST

/payments/{id}/refund

Refund a payment

POST

/subscriptions

Create a subscription

POST

/bizum/validate-phone

Validate a Bizum phone number

POST

Why Jentic?

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

Credential isolation

MONEI Authorization API keys and per-merchant MONEI-Account-ID values are stored encrypted in the Jentic vault. Agents receive scoped tokens at execution time so raw secrets never enter the model context, even on multi-tenant platforms.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a card payment in Spain') and Jentic returns the matching MONEI operations with their input schemas, so the agent picks the right endpoint without browsing developer docs.

Time to first call

Direct MONEI integration: 2-4 days for auth, webhook handling, SCA flows, and refund logic. Through Jentic: under 1 hour to search, load the schema, and execute the first live payment.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe API

Global payment gateway with broader currency and method coverage but no native Bizum

Choose Stripe over MONEI when the merchant operates outside Spain or needs Stripe Connect, Issuing, or Tax in addition to acquiring.

Alternative

Adyen Checkout API

Enterprise European acquirer with single-platform card, wallet, and local method support

Choose Adyen Checkout when the merchant needs unified processing across many European countries with one contract and higher transaction volumes.

Alternative

Braintree API

PayPal-owned gateway with strong wallet support but limited Spanish local methods

Use Braintree when the merchant already runs on PayPal and wants Venmo or PayPal as primary methods rather than Bizum.

Complementary

PayPal Payments API

Add PayPal wallet alongside MONEI's card and Bizum acceptance

Pair with MONEI when the merchant wants to offer PayPal as an additional checkout option and reconcile both gateways in the same workflow.

FAQs

Specific to using MONEI API v1 API through Jentic.

What authentication does the MONEI API use?

MONEI uses an API key passed in the Authorization header, with an optional MONEI-Account-ID header for platforms acting on behalf of a connected merchant. Through Jentic the key lives in the credential vault and is injected at execution time, so the agent never sees the raw secret.

Can I accept Bizum with the MONEI API?

Yes. Call POST /bizum/validate-phone with the Spanish mobile number to confirm it is registered for Bizum, then create a payment on POST /payments with Bizum selected as the method. MONEI returns a payment URL or a status the customer's bank app uses to confirm.

What are the rate limits for the MONEI API?

MONEI returns HTTP 429 Too Many Requests when limits are exceeded. The exact per-second quota is not published in the spec; back off on 429 and retry with exponential delay. All requests must be HTTPS and include a valid User-Agent header or they are rejected with 401.

How do I issue a refund through Jentic?

Search Jentic for 'refund a MONEI payment', load the schema for POST /payments/{id}/refund, and execute it with the payment id and refund amount. Jentic handles the Authorization header so you only supply the business inputs.

Does MONEI support recurring subscriptions?

Yes, the /subscriptions resource provides create, retrieve, pause, resume, update plan, and cancel operations. Each billing cycle generates a child payment that can be reconciled or refunded individually like any other MONEI payment.

How do I register an Apple Pay domain on MONEI?

Provision a merchant certificate through POST /apple-pay/certificates, activate it on POST /apple-pay/certificates/{id}/activate, then register each checkout domain on POST /apple-pay/domains. The domain must serve the Apple Pay verification file at the well-known path before it is accepted.