Skip to content
Hypamoon

Payments and billing

Connect Redsys to Hypamoon

Yes, with one catch. Redsys has an open API that you can use yourself, but it signs in with OAuth only, and that takes more work in a Hypamoon adapter today.

Open

The check

Three questions about the API of Redsys, answered from its own docs.

Public API docs
Yes. Read the docs
A key you create yourself
Yes. The signing key is shown in the TPV Virtual administration portal under the merchant data, per terminal. pagosonline.redsys.es
Versions or a changelog
Yes. Release notes for the downloadable libraries, and a signature version in each request. pagosonline.redsys.es
How it signs in
Each request carries the merchant code (FUC) and terminal, signed with the terminal's secret signing key.
Webhooks
Yes. It can tell your app when something changes. pagosonline.redsys.es
Hosting
Cloud
Condition
You contract the TPV Virtual through a bank that processes with Redsys; the bank gives you the merchant code.

Your own order and payment check on Redsys, so every paid order is confirmed once.

  • Payments and their results, from the Redsys REST API and the signed notification to your server.
  • AI that spots orders where the notification never arrived, with you deciding what to follow up.
  • A screen for your team and an email when an order needs a look.

Ask your chat

Answers straight from your Redsys data, in Claude or another chat with the full Hypamoon connection.

  • Which orders from today have no payment result yet?
  • How many payments were declined this week?

When something happens

Redsys sends a webhook to your app, and the app asks AI what happens next.

  1. When

    Redsys posts the result of a payment to your server.

    AI decides

    AI checks the signature, the amount and the order.

    Then

    The order is marked paid in your app, or your team gets an email if something is off.

A screen for your team or customers

An app on your own address, with sign-in, on top of the same Redsys data.

  • For your team

    Your team sees the day's orders with their payment result.

Redsys stays the core: your chat builds the rest on its API, as an adapter plus an app and agents in your Hypamoon project. Reading starts after you click Allow in the portal. Every change an agent or a chat makes in Redsys waits for your approval, one call at a time. How adapters work

Good to know

  • Redsys signs in with OAuth or signed requests only, with tokens that expire. The Hypamoon vault holds a fixed key today, so an adapter for Redsys takes more work: ask your chat to check this first.
  • Never confirm an order on the customer's return URL; use the signed server notification.

Try it in your chat

Fill in what to read and write, and send it.

Say this in your chat

Build the Hypamoon recipe build-an-adapter for Redsys. API docs: https://pagosonline.redsys.es/desarrolladores-inicio/documentacion-operativa/autorizacion/. Read: [what]. Write: [what, or nothing].

In Claude, or another chat with the full Hypamoon connection; adapters are not in ChatGPT yet. You paste the key in the portal, never in the chat. The full recipe

Sources

Checked on 7 November 2026.

Redsys is a name of its owner, used here only to describe the software. This page is not an official integration and Hypamoon has no partnership with Redsys. Found something that changed? Tell us at support.

More in payments and billing

All 1094 tools

Tool not listed? Ask the chat to check its API.

The same three checks work for any software. Your chat reads the vendor's own docs and tells you what it found.

Say this in your chat

Check if [software] has an open API that a Hypamoon adapter can use: public API docs, a key or token I can create myself without asking the vendor, and versions or a changelog. Link the pages you used.

Fill in the name of your software. Checking needs no connection to Hypamoon.

Ready to connect Redsys?

Connect your chat once, then ask it to build the adapter.

Works in Claude, ChatGPT and Copilot. Add to Claude Add to ChatGPT Add to Copilot