Changelog

What's new in the MONEI docs and product. Newest first.

September 2026

• Adobe Commerce (Magento 2): express checkout and separate card fields. Module 2.4.0 adds Apple Pay, Google Pay and PayPal express checkout on the cart, mini cart and product page, and makes separate card fields the default card form — both documented with the settings and what the customer sees.

• The PrestaShop guide now covers card layouts and express checkout. You can choose a single-line or split card form — both shown with screenshots, and both now inherit your theme's own field styling instead of a fixed look. Express checkout, an Apple Pay, Google Pay or PayPal button on the product and cart pages, is documented for the first time — including why it no longer appears on the checkout payment step.

• WooCommerce: the text in the card fields is centred. From plugin v7.3.3 the card number, expiry and CVC render their text in the vertical middle of the field, on both layouts. A Card Input Style with its own height is left as you set it — use the field's inner height, 48px by default, to keep the text centred.

• What bringing your own acquirer actually costs. The 0.20% of GPV is charged instead of MONEI's per-transaction fee, not on top of it — the pricing page implied the opposite by listing it among the technology services "billed on top of your per-transaction fees". Bring your own acquirer is now its own section with a worked example: on a €250 payment routed to your own acquirer you pay MONEI €0.50, not €3.00. It also states what does still apply — the €0.15 daily platform fee — and that your own bank settles those payments directly, so MONEI's settlement period and rolling reserve don't.

• SEPA Request to Pay is a closed beta, not a payment method you can accept. The page read as if merchants could offer SRTP at checkout; it now says up front that access is by invitation for payer-side SRTP service providers only, and the payment methods overview answers whether MONEI supports SEPA Direct Debit or SEPA Request to Pay — neither is available to merchants. The Medusa and commercetools pages no longer list SEPA Direct Debit.

• Machine-readable access now covers the Spanish docs too. The Spanish corpus has its own page index and canonical URL list — /es/llms.txt and /es/sitemap.xml, both announced in robots.txt — and Spanish pages now point at the Spanish index instead of the English one. See what is available.

• Earn discounts now lists the offers that actually exist. The page described a fee discount for writing a Google review, which is no longer offered, and mentioned neither of the two ways that are: a 100% discount for a week for posting about MONEI on LinkedIn and the Affiliate Program. It also states the limits for the first time — Spain only, €300 maximum.

• Connect your own Redsys TPV Virtual on MONEI One, and route between processors on any plan. The credentials form used to appear only on the legacy MONEI PLUS plan, leaving every other account an upgrade message. It now appears on MONEI One, so you can enter your TPV Virtual credentials in Settings → Payment methods yourself; accounts still on a legacy plan can ask support to switch them. Per-processor routing rules are no longer tied to a plan at all and are configurable on every account.

• The per-payment limit is now set per point of sale. It was a flat 3,000.00 EUR for everyone; it is still the default, but MONEI support can raise it for a single point of sale up to 100,000.00 EUR — MONEI's own per-payment maximum — which is what makes Cuaderno 60 municipal bills above 3,000 EUR (IBI, plusvalías, sanctions) collectable at all. The same applies to manually entered amounts, and the payer's own card or Bizum limit still applies.

• A missed deadline is no longer filed as a loss. Disputes whose response window closed unanswered now carry their own Expired status and their own tab, instead of being mixed into Lost with the cases you argued and lost. The money outcome is the same; what changes is that you can now see which deadlines are being missed.

• Every dispute reason code, and the documents that answer it. A new reference page lists every reason code MONEI recognises — Visa's 10.x, 11.x, 12.x and 13.x families and Mastercard's 48xx codes — with what the cardholder is claiming under each one and which documents best support your response. It is the same guidance the Dashboard shows behind What documents can support my case?

• One name for the redirect checkout: the Hosted Payment Page. The same product was called a prebuilt payment page, a hosted page and a MONEI-hosted page across the docs, and the page itself was titled "Use a prebuilt payment page". Everything now says Hosted Payment Page, and that page states plainly that it is the redirect-based checkout, so a search for "redirect" finds it.

• Hotels: the docs now answer "can I use MONEI with Hotelgest?". The Hotels page covered only channel-manager tokenization, so a hotelier asking about a PMS was told MONEI supports Siteminder and Channex and nothing else. It now separates the two routes and confirms that Hotelgest hotels can accept MONEI through Hotelgest as a MONEI Connect partner.

• MONEI is available in Spain and Andorra only. Where MONEI is available said that bringing your own acquirer or processor made MONEI available worldwide. That isn't the case: a business must be registered in Spain or Andorra either way. The outside-Spain answer is corrected to match.

• MONEI Flex is PlazoX, and the page now says so. Shoppers and merchants know the bank installment service by its own name, so MONEI Flex explains that it is the same PlazoX their bank offers, appearing at checkout as PlazoX and PlazoX cero.

• The docs now say what MONEI does not do. Ten limitations are written down for the first time, each as a question you can link to: no American Express, no MOTO or virtual terminal, no SEPA Direct Debit, one capture per authorization and never above the authorized amount, built-in acquiring in Spain and Andorra only, no account balance and no long-term holding, no stablecoin settlement, nothing shared between accounts, no idempotency key on the API, and raw card data only with PCI DSS certification.

• Webhook retries now back off over three days, and an endpoint survives a bad day. The retry policy is documented for the first time: 18 attempts with growing gaps, seconds to 11 hours, spread over about three days. An endpoint is disabled only after seven days of failing with no success in between, where any single success resets the clock. Events are never queued for later, so reconcile from the API rather than assuming delivery.

• Refunds have a deadline, per payment method. The refunds page said a refund could be issued at any time. It now carries the deadline for each method — 180 days for cards, Bizum and PayPal, 13 months for MB WAY and Multibanco — plus what you can't do: refund above the original amount or to another destination.

August 2026

• The documentation is now readable by AI agents. Every page also serves Markdown — drop the trailing slash and append .md — and the docs search index is reachable two ways: a hosted MCP server that needs no key or install, and the search API directly over HTTP. See Documentation for AI agents.

• Disputes now have one tab per status. The Disputes list splits into Inquiries · Needs response · Under review · Won · Lost · Closed · All, so a won case no longer sits in the same tab as a lost one, and you land on Needs response — the only queue you can act on. The response deadline also turns red in its final two days. See Find a dispute and The deadline.

• WooCommerce: separate card fields are the default. From plugin v7.3.0 the card form shows card number, expiry and CVC as three separate fields instead of one line. A store that already chose a layout keeps it; one that never did moves to separate fields on update, and can switch back under MONEI Cards.

• A closed dispute doesn't always mean nothing was taken. The Inquiry closed status is now simply Closed, because a dispute settled before it became a chargeback — through Visa RDR or a Mastercard Ethoca alert — refunds the cardholder and reaches you as a deduction on your payout, with no chargeback or dispute fee. See Read the status.

• Answer a chargeback from the Dashboard. A new Disputes section lists every chargeback and inquiry on your account, and you can now write your argument, attach evidence, and file a response before the deadline — one response per chargeback, so read the evidence limits first.

• WooCommerce: Apple Pay and Google Pay now pre-authorize, and a capture always completes. In plugin v7.2.4, Payment Action set to Authorization applies to the two wallet methods as well, which used to charge immediately regardless. Capture also runs wherever the order status changes — a shipping plugin, an ERP sync or the REST API moving an order to Processing previously left the money held until the authorization expired.

• WooCommerce: pre-authorization, subscriptions, refunds and saved cards, documented. The WooCommerce page now covers holding money and capturing it later by moving the order status, recurring billing with WooCommerce Subscriptions or YITH, refunding from the order screen, saved cards, and what to check when a method is missing at checkout or an order stays Pending.

• PayPal returns the shopper's name and email without shipping. A store that sells digital goods has no shipping methods, so PayPal express checkout returned only a token — not enough to place the order. Payer details now come back on every PayPal payment, and shipping details stay tied to requestShipping. See SubmitResult.

• WooCommerce: express checkout, and a choice of card field layout. Apple Pay, Google Pay and PayPal buttons now sit on the product, cart and checkout pages so shoppers pay straight from the wallet sheet, and the card form takes a one-line or separate-field layout, in plugin v7.1.0.

• Payout timing, in plain terms. Settlement periods now read as D+1 and D+7 — day plus N instead of T+N, your first payout arrives after 30 days rather than up to 30, and a shorter period is assigned automatically as your account builds a low-risk track record — it can't be requested on approval.

• Card transaction limits go by sector, and high-ticket sectors are up to 15,000 EUR. The 4,000 EUR maximum per card transaction is a default: the ceiling above it is set per business sector, the sectors reviewed so far are at 15,000 EUR, and a lower maximum can be set on your own account on request.

• What a payout's ⋯ menu holds. A payout in Settings → Payouts offers Preview — the breakdown that carries its reserved and released amounts — and Download operations file, which is in the menu only while the payout's status is Completed.

• Split card fields for custom checkouts. Mount the card number, expiry and CVC as three independent Components anywhere in your checkout markup — a CardGroup coordinates them and tokenizes, focus advances automatically as the customer types, and your PCI DSS scope stays at SAQ A. Available in the React, Vue, Angular and Svelte packages, with a new Migrate from Stripe guide that maps Stripe Elements concepts one-to-one.

• Tell us where you sell, and skip the website if you sell in person. The Business details step asks Where do you accept payments? — pick In person and no website is required, so you sell with the MONEI Pay app, QR codes at your points of sale, and Pay by Link, while an API key and the e-commerce integrations wait until you add the online sales channel and we verify your website.

• Copy your business data into a second account, and switch between them. The Create another account dialog carries a Copy business data to the new account? option, so a second account reuses the details of the one you are in — and every account on your login is one Switch account away. See multiple accounts.

• Activation asks companies and autónomos for different documents. The Business details step adapts to your legal form: a Company enters its Tax Identification Number (CIF) and MONEI looks it up in the commercial registry, while a Self-employed merchant picks a tax registry — Agencia Tributaria, or the foral office of Gipuzkoa, Navarra or Bizkaia — and provides a certificate of census situation (Modelo 036 is not accepted).

• Send a subscription link from the Dashboard. You no longer need the API to send an activation link: open the subscription and send it from the Dashboard by Email, WhatsApp, or SMS, in the customer's own language, after checking the email preview.

• The Shopify integration screen, as it is now. Configuring a Shopify app is at Settings → Payments → Integrations → Shopify, which lists Connected Shopify stores; a row's actions are on its ··· menu, where Configure sets test mode and assigns a MONEI store per checkout country. Disconnect a store by uninstalling the MONEI app from your Shopify admin.

• Your branding also brands your QR codes. The Icon and Primary color you set in Branding are the icon at the centre of your QR codes and the colour they are drawn in.

• Salesforce: the plugin's Password is your API key. Configuring the Salesforce plugin now names the two dashboard values as they render — Your Account ID and Your API Key — and says the Activate button is in Business Manager, not in MONEI.

• Fraud risk shields, decoded. Reviewing fraud analysis on a payment now maps each shield color in the payments list to its risk level and score band — green for low (0–49), orange for medium (50–94), red for high (95–100) — and explains why a high-risk payment can still succeed.

• Cuaderno 60 exports over a custom range. The C60 reconciliation export is no longer limited to a quincena — pick any range of up to 92 days instead.

• Payment dates, explained. The payments list and Payment events use different dates — a payment created yesterday and refunded today keeps yesterday's date in the payments list, while the refund appears under today in Payment events.

• Transaction history, in full. Transaction history now covers the status tabs above the payments table, the date range that starts at today, filtering one field at a time as removable chips with Clear all, an Export that honours those filters, the payment Timeline, and the Payment events stream.

• Dashboard screen names and links, corrected. Dashboard steps now quote the screen name you see in the settings menu — Settings → Payment methods, Settings → Points of sale, Settings → Authorized users, Settings → API Access, Settings → Earn discounts and Settings → Apple Pay certificates — and the Pay by Link button in configure payment methods plus the webhook-delivery check in QR payments now link to the screen they describe.

• Permanent payment links and short links. A QR code's URL now has a full guide: use it as a permanent payment link that never expires, shorten it to a custom monei.me short link you can print, and pick the right tool for each sale in QR codes and payment links.

• Allowlist, and one screen for both lists. The blacklist is now the blocklist and shares Settings → Allow & block lists with the new allowlist, which exempts a trusted customer's email address or device from being blocked — and the blocklist now also accepts card and device fingerprints.

• Bancontact. Accept Bancontact, Belgium's most popular local payment method — enable it in your dashboard and the button appears on your payment page for customers in Belgium.

June 2026

• MONEI Flex card installments. Spanish customers can now split a card purchase into monthly installments — interest-free over 3 months, or over 3, 6, or 12 months financed by their own bank — decided instantly at checkout, while you're paid in full upfront. See MONEI Flex.
• Stronger account sign-in. Text-message (SMS) two-step authentication is now required for every user on a live account, and you can add an authenticator app for faster, offline sign-in. At sign-in, MONEI remembers your last-used method and lets you switch methods if you can't access it.
• Payments for public administrations. A new Public Administrations vertical for municipalities, tax agencies, and public institutions — including Cuaderno 60 (AEB 60012): citizens pay preprinted notices by QR code or monei.me link, and you export the reconciliation fichero for your bank.
• Tap to Pay in MONEI Pay. Accept contactless cards, Apple Pay, and Google Pay directly on your phone — no card reader or dongle — on iPhone and Android.
• Launch MONEI Pay with a Universal Link. Trigger a payment from your own app or website using an https://pay.monei.com/accept-payment Universal Link (iOS) / App Link (Android) that opens MONEI Pay directly, with no confirmation prompt.

May 2026

• Payments glossary + inline definitions. A new glossary defines payment terms in plain language, and obscure terms now show a definition when you click them across the docs.
• Payments orchestration, rebuilt. Orchestration now documents rule conditions and the full set of actions — route to a processor, split traffic, hide payment methods, block a processor, and decline — plus when rules are evaluated.
• Send payouts to customers. New guide for paying customers with Bizum or card, including the prefunded-balance model and how to get access.
• Point-of-sale payment settings. Stores and points of sale now covers per-POS payment callback URLs, fixed amounts, requiring email / tax ID, and the order-QR receipt for event ticketing and click & collect.
• Settlement clarity. Payouts and settlements explains how to download a payout's operations file and how the settlement period is calculated (UTC).
• New account pages. Profile and security, email notifications, and legal documents (download your signed contract).
• Diagrams. Visual flows added for webhooks, the payment lifecycle, 3D Secure, chargebacks, customer payouts, stores & points of sale, saving a payment method, and account activation.