Recurring Recurring Details Request Structure

{
  "$schema": "https://json-structure.org/meta/core/v0/#",
  "$id": "https://raw.githubusercontent.com/api-evangelist/adyen/refs/heads/main/json-structure/recurring-recurring-details-request-structure.json",
  "description": "RecurringDetailsRequest schema from Adyen API",
  "type": "object",
  "properties": {
    "merchantAccount": {
      "description": "The merchant account identifier you want to process the (transaction) request with.",
      "type": "string"
    },
    "recurring": {
      "description": "A container for the type of a recurring contract to be retrieved.\n\nThe contract value needs to match the contract value submitted in the payment transaction used to create a recurring contract.\nHowever, if `ONECLICK,RECURRING` is the original contract definition in the initial payment, then `contract` should take either `ONECLICK` or `RECURRING`, depending on whether or not you want the shopper to enter their card's security code when they finalize their purchase.",
      "$ref": "#/components/schemas/Recurring"
    },
    "shopperReference": {
      "description": "The reference you use to uniquely identify the shopper (e.g. user ID or account ID).",
      "type": "string"
    }
  },
  "required": [
    "merchantAccount",
    "shopperReference"
  ],
  "name": "RecurringDetailsRequest"
}