For Agents
Issue, load, balance-check, merge, status-change, and void transactions on Adyen-issued gift and stored-value cards.
Get started with Adyen Stored Value API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"issue an Adyen gift card"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Adyen Stored Value API 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
Merge the remaining balance of two cards into one via POST /mergeBalance
GET STARTED
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.
The Adyen Stored Value API manages gift cards, prepaid cards, and other stored-value payment instruments issued through Adyen. The six endpoints cover card issuance, balance inquiries, loading funds onto a card, merging two card balances, voiding a previous transaction, and changing card status (for example to lock a lost card). It is the integration surface for retailers and brands running their own gift card or e-wallet programmes on Adyen rails.
Void a previous stored-value transaction via POST /voidTransaction by reference
Change a card's status via POST /changeStatus to lock, unlock, or expire a stored-value card
Patterns agents use Adyen Stored Value API 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
6 endpoints — the adyen stored value api manages gift cards, prepaid cards, and other stored-value payment instruments issued through adyen.
METHOD
PATH
DESCRIPTION
/issue
Issue a new stored-value card
/load
Load funds onto a card
/checkBalance
Check the available balance
/mergeBalance
Merge two card balances
/changeStatus
Change card status (lock, unlock)
/voidTransaction
Void a previous stored-value transaction
/issue
Issue a new stored-value card
/load
Load funds onto a card
/checkBalance
Check the available balance
/mergeBalance
Merge two card balances
/changeStatus
Change card status (lock, unlock)
Three things that make agents converge on Jentic-routed access.
Credential isolation
Adyen API keys and basic-auth credentials are stored encrypted in the Jentic vault. Agents receive scoped access tokens at execution time — the raw X-API-Key value never enters the agent context.
Intent-based discovery
Agents search by intent (e.g., 'issue a gift card' or 'check stored-value balance') and Jentic returns the matching issue or checkBalance operation with its full input schema, so the agent picks the right endpoint without browsing Adyen's stored-value docs.
Time to first call
Direct Adyen Stored Value integration: 2-4 days for issuance flow, balance reconciliation, and lost-card handling. Through Jentic: under 1 hour — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Adyen Payment API
Authorise card payments that may be funded by a stored-value card
Use Payment API alongside Stored Value when a checkout combines a gift card and a regular card payment
Adyen Checkout API
Modern checkout surface that supports gift card payment methods
Use Checkout when accepting gift cards at the front end and Stored Value to manage the cards' issuance and balances
Adyen BIN Lookup API
Identify card BIN attributes before issuing or loading
Use BIN Lookup to validate or classify a card brand before invoking Stored Value endpoints on it
Adyen Recurring API
Stores payment tokens for cards rather than stored-value balances
Choose Recurring when storing reusable card credentials for subscriptions; choose Stored Value when running a gift or prepaid programme
Specific to using Adyen Stored Value API 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 at https://app.jentic.com/sign-up.
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.
/voidTransaction
Void a previous stored-value transaction