Adyen · Schema

NotifyShopperRequest

NotifyShopperRequest schema from Adyen API

PaymentsFinancial-ServicesFintech

Properties

Name Type Description
amount object The amount of the upcoming payment.
billingDate string Date on which the subscription amount will be debited from the shopper. In YYYY-MM-DD format
billingSequenceNumber string Sequence of the debit. Depends on Frequency and Billing Attempts Rule.
displayedReference string Reference of Pre-debit notification that is displayed to the shopper. Optional field. Maps to reference if missing
merchantAccount string The merchant account identifier with which you want to process the transaction.
recurringDetailReference string This is the `recurringDetailReference` returned in the response when you created the token.
reference string Pre-debit notification reference sent by the merchant. This is a mandatory field
shopperReference string The ID that uniquely identifies the shopper. This `shopperReference` must be the same as the `shopperReference` used in the initial payment.
storedPaymentMethodId string This is the `recurringDetailReference` returned in the response when you created the token.
View JSON Schema on GitHub

JSON Schema

recurring-notify-shopper-request-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/adyen/refs/heads/main/json-schema/recurring-notify-shopper-request-schema.json",
  "title": "NotifyShopperRequest",
  "description": "NotifyShopperRequest schema from Adyen API",
  "type": "object",
  "properties": {
    "amount": {
      "description": "The amount of the upcoming payment.",
      "$ref": "#/components/schemas/Amount"
    },
    "billingDate": {
      "description": "Date on which the subscription amount will be debited from the shopper. In YYYY-MM-DD format",
      "type": "string"
    },
    "billingSequenceNumber": {
      "description": "Sequence of the debit. Depends on Frequency and Billing Attempts Rule.",
      "type": "string"
    },
    "displayedReference": {
      "description": "Reference of Pre-debit notification that is displayed to the shopper. Optional field. Maps to reference if missing",
      "type": "string"
    },
    "merchantAccount": {
      "description": "The merchant account identifier with which you want to process the transaction.",
      "type": "string"
    },
    "recurringDetailReference": {
      "description": "This is the `recurringDetailReference` returned in the response when you created the token.",
      "type": "string"
    },
    "reference": {
      "description": "Pre-debit notification reference sent by the merchant. This is a mandatory field",
      "type": "string"
    },
    "shopperReference": {
      "description": "The ID that uniquely identifies the shopper.\n\nThis `shopperReference` must be the same as the `shopperReference` used in the initial payment.",
      "type": "string"
    },
    "storedPaymentMethodId": {
      "description": "This is the `recurringDetailReference` returned in the response when you created the token.",
      "type": "string"
    }
  },
  "required": [
    "merchantAccount",
    "shopperReference",
    "amount",
    "reference"
  ]
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/recurring-notify-shopper-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.