Adyen Stored Value API

Name: Adyen Stored Value API
Brand: Adyen Stored Value API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey, basic6 EndpointsREST

Install Jentic One Beta

Connect the Adyen Stored Value API to your agent

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

Issue a new stored-value card via POST /issue with brand, currency, and load amount

Check the available balance on a stored-value card via POST /checkBalance

Load additional funds onto a card via POST /load

GET STARTED

Start building with Adyen Stored Value API

Explore with Jentic

View OpenAPI Document

For Agents

Issue, load, balance-check, merge, status-change, and void transactions on Adyen-issued gift and stored-value cards.

Use for: Issue a new gift card with a 50 EUR starting balance, Check the remaining balance on a stored-value card, Load additional funds onto an existing prepaid card, Merge the balance of an old gift card into a new one

Not supported: Does not process credit-card payments, manage payouts, or run loyalty rewards - use only for issuing, loading, and managing Adyen stored-value cards.

Use Cases

Patterns agents use Adyen Stored Value API for, with concrete tasks.

★ Retailer Gift Card Issuance

Retailers running their own gift card programme call POST /issue with the merchantAccount, paymentMethod (gift card brand), and an initial loadAmount. Adyen returns a recurringDetailReference and card data that the retailer can either email to the buyer or print onto a physical card. POST /load tops the same card up later - for example, when a customer adds value at the till - and POST /checkBalance powers self-service balance lookups.

Call POST /issue with paymentMethod.type and brand for the gift card, loadAmount.value=5000, loadAmount.currency=EUR, and merchantAccount, then POST /checkBalance with the returned recurringDetailReference

Lost-Card Lock and Balance Migration

When a customer reports a stored-value card lost, POST /changeStatus locks the original card so it can no longer be used, and POST /mergeBalance moves its remaining balance to a freshly issued replacement. This preserves the customer's funds while preventing further use of the lost card. The replacement is issued via POST /issue and the merge runs against both card references.

Call POST /changeStatus with the lost card's reference and status=Active=false, then POST /mergeBalance with sourceCard and targetCard references to move funds to the replacement

Reversal of Stored-Value Transactions

When a stored-value transaction is mistakenly applied - wrong amount loaded, wrong card chosen at checkout - POST /voidTransaction reverses it by originalReference. This restores the card balance to its previous state without going through a manual refund flow. It is the standard correction path for stored-value programmes.

Call POST /voidTransaction with originalReference set to the pspReference of the transaction to reverse and merchantAccount

AI Agent Gift Card Operations via Jentic

A retail operations agent that issues bulk corporate gift cards searches Jentic for 'issue an Adyen gift card', loads the schema for /issue, and executes once per recipient from a CSV. Jentic injects X-API-Key from the encrypted vault and the agent never touches the raw secret. The agent records each returned recurringDetailReference and load amount in the customer database.

Search Jentic for 'issue an Adyen gift card', load the issue schema, then execute one call per recipient row in the corporate gift card CSV

Key Endpoints

6 endpoints — the adyen stored value api manages gift cards, prepaid cards, and other stored-value payment instruments issued through adyen.

METHOD

PATH

DESCRIPTION

POST

/issue

Issue a new stored-value card

POST

/load

Load funds onto a card

POST

/checkBalance

Check the available balance

POST

/mergeBalance

Merge two card balances

POST

/changeStatus

Change card status (lock, unlock)

POST

/voidTransaction

Void a previous stored-value transaction

POST

/issue

Issue a new stored-value card

POST

/load

Load funds onto a card

POST

/checkBalance

Check the available balance

POST

/mergeBalance

Merge two card balances

POST

/changeStatus

Change card status (lock, unlock)

POST

Why Jentic?

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

Credential isolation

Your Adyen X-API-Key and basic auth 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.

Intent-based discovery

Agents search Jentic by intent such as 'issue a gift card' or 'check a stored-value balance', and Jentic returns the matching Stored Value operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Adyen Stored Value API through Jentic.

What authentication does the Adyen Stored Value API use?

The API supports an API key in the X-API-Key header (ApiKeyAuth) and HTTP Basic auth (BasicAuth) using web-service user credentials. Through Jentic, credentials are stored encrypted in the vault and only a scoped execution token is exposed to the agent.

Can I issue a gift card programmatically with the Adyen Stored Value API?

Yes. POST /issue creates a new stored-value card and returns a recurringDetailReference identifying it, along with the card data needed to either deliver it digitally or imprint it onto a physical card. Pass the brand on paymentMethod, the initial loadAmount, and merchantAccount.

How do I check the balance of a stored-value card?

POST /checkBalance returns the current and authorised balances on the card identified by recurringDetailReference. This is the standard endpoint for self-service balance lookups in retailer apps and for backend reconciliation.

What are the rate limits for the Adyen Stored Value API?

Adyen does not publish a fixed numeric rate limit in the spec; throughput is provisioned per merchant account based on programme volumes. If 429 responses appear, contact Adyen support to review the limits for the stored-value programme.

How do I issue a gift card with the Stored Value API through Jentic?

Search Jentic for 'issue an Adyen gift card', load the issue schema, then execute with paymentMethod.type, brand, loadAmount.value, loadAmount.currency, and merchantAccount. Jentic injects X-API-Key from the encrypted vault. Get an account through Jentic One, the self-hosted execution layer.

Can I move balance from one stored-value card to another?

Yes. POST /mergeBalance accepts a source card reference and a target card reference and moves the remaining balance from source to target. This is the recommended pattern for replacing lost cards: issue a new card, lock the old one with POST /changeStatus, then merge the balance to the replacement.

Can I limit what my agent is allowed to do with the Adyen Stored Value API?

Yes. Jentic One is self-hosted, so your own rules decide which Stored Value operations the agent may call and which credentials it may use. Because the API passes card and account references in the request body rather than in the URL path, you choose the operations to expose, so you can allow read-only checks like POST /checkBalance while keeping POST /issue, POST /load, POST /changeStatus, and POST /voidTransaction out of reach unless you include them. Your Adyen API key and basic auth credentials stay stored on your instance and are injected only at execution, never entering the agent's prompt or logs.

Adyen Stored Value API

Connect the Adyen Stored Value API to your agent

Capabilities

Start building with Adyen Stored Value API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs