Skip to content

Commit

Permalink
spec release
Browse files Browse the repository at this point in the history
  • Loading branch information
Adyen Automation committed Sep 20, 2024
1 parent b1dc7a0 commit 17347a5
Show file tree
Hide file tree
Showing 22 changed files with 88 additions and 0 deletions.
4 changes: 4 additions & 0 deletions json/PaymentService-v25.json
Original file line number Diff line number Diff line change
Expand Up @@ -2377,6 +2377,10 @@
"description" : "The number of the day, on which the recurring debit can happen. Should be within the same calendar month as the mandate recurring date.\n\nPossible values: 1-31 based on the `frequency`.",
"type" : "string"
},
"count" : {
"description" : "The number of transactions that can be performed within the given frequency.",
"type" : "string"
},
"endsAt" : {
"description" : "End date of the billing plan, in YYYY-MM-DD format.",
"type" : "string"
Expand Down
4 changes: 4 additions & 0 deletions json/PaymentService-v30.json
Original file line number Diff line number Diff line change
Expand Up @@ -2727,6 +2727,10 @@
"description" : "The number of the day, on which the recurring debit can happen. Should be within the same calendar month as the mandate recurring date.\n\nPossible values: 1-31 based on the `frequency`.",
"type" : "string"
},
"count" : {
"description" : "The number of transactions that can be performed within the given frequency.",
"type" : "string"
},
"endsAt" : {
"description" : "End date of the billing plan, in YYYY-MM-DD format.",
"type" : "string"
Expand Down
4 changes: 4 additions & 0 deletions json/PaymentService-v40.json
Original file line number Diff line number Diff line change
Expand Up @@ -3386,6 +3386,10 @@
"description" : "The number of the day, on which the recurring debit can happen. Should be within the same calendar month as the mandate recurring date.\n\nPossible values: 1-31 based on the `frequency`.",
"type" : "string"
},
"count" : {
"description" : "The number of transactions that can be performed within the given frequency.",
"type" : "string"
},
"endsAt" : {
"description" : "End date of the billing plan, in YYYY-MM-DD format.",
"type" : "string"
Expand Down
4 changes: 4 additions & 0 deletions json/PaymentService-v46.json
Original file line number Diff line number Diff line change
Expand Up @@ -3406,6 +3406,10 @@
"description" : "The number of the day, on which the recurring debit can happen. Should be within the same calendar month as the mandate recurring date.\n\nPossible values: 1-31 based on the `frequency`.",
"type" : "string"
},
"count" : {
"description" : "The number of transactions that can be performed within the given frequency.",
"type" : "string"
},
"endsAt" : {
"description" : "End date of the billing plan, in YYYY-MM-DD format.",
"type" : "string"
Expand Down
4 changes: 4 additions & 0 deletions json/PaymentService-v49.json
Original file line number Diff line number Diff line change
Expand Up @@ -3406,6 +3406,10 @@
"description" : "The number of the day, on which the recurring debit can happen. Should be within the same calendar month as the mandate recurring date.\n\nPossible values: 1-31 based on the `frequency`.",
"type" : "string"
},
"count" : {
"description" : "The number of transactions that can be performed within the given frequency.",
"type" : "string"
},
"endsAt" : {
"description" : "End date of the billing plan, in YYYY-MM-DD format.",
"type" : "string"
Expand Down
4 changes: 4 additions & 0 deletions json/PaymentService-v50.json
Original file line number Diff line number Diff line change
Expand Up @@ -3416,6 +3416,10 @@
"description" : "The number of the day, on which the recurring debit can happen. Should be within the same calendar month as the mandate recurring date.\n\nPossible values: 1-31 based on the `frequency`.",
"type" : "string"
},
"count" : {
"description" : "The number of transactions that can be performed within the given frequency.",
"type" : "string"
},
"endsAt" : {
"description" : "End date of the billing plan, in YYYY-MM-DD format.",
"type" : "string"
Expand Down
4 changes: 4 additions & 0 deletions json/PaymentService-v51.json
Original file line number Diff line number Diff line change
Expand Up @@ -3562,6 +3562,10 @@
"description" : "The number of the day, on which the recurring debit can happen. Should be within the same calendar month as the mandate recurring date.\n\nPossible values: 1-31 based on the `frequency`.",
"type" : "string"
},
"count" : {
"description" : "The number of transactions that can be performed within the given frequency.",
"type" : "string"
},
"endsAt" : {
"description" : "End date of the billing plan, in YYYY-MM-DD format.",
"type" : "string"
Expand Down
4 changes: 4 additions & 0 deletions json/PaymentService-v52.json
Original file line number Diff line number Diff line change
Expand Up @@ -3562,6 +3562,10 @@
"description" : "The number of the day, on which the recurring debit can happen. Should be within the same calendar month as the mandate recurring date.\n\nPossible values: 1-31 based on the `frequency`.",
"type" : "string"
},
"count" : {
"description" : "The number of transactions that can be performed within the given frequency.",
"type" : "string"
},
"endsAt" : {
"description" : "End date of the billing plan, in YYYY-MM-DD format.",
"type" : "string"
Expand Down
4 changes: 4 additions & 0 deletions json/PaymentService-v64.json
Original file line number Diff line number Diff line change
Expand Up @@ -3653,6 +3653,10 @@
"description" : "The number of the day, on which the recurring debit can happen. Should be within the same calendar month as the mandate recurring date.\n\nPossible values: 1-31 based on the `frequency`.",
"type" : "string"
},
"count" : {
"description" : "The number of transactions that can be performed within the given frequency.",
"type" : "string"
},
"endsAt" : {
"description" : "End date of the billing plan, in YYYY-MM-DD format.",
"type" : "string"
Expand Down
4 changes: 4 additions & 0 deletions json/PaymentService-v67.json
Original file line number Diff line number Diff line change
Expand Up @@ -3653,6 +3653,10 @@
"description" : "The number of the day, on which the recurring debit can happen. Should be within the same calendar month as the mandate recurring date.\n\nPossible values: 1-31 based on the `frequency`.",
"type" : "string"
},
"count" : {
"description" : "The number of transactions that can be performed within the given frequency.",
"type" : "string"
},
"endsAt" : {
"description" : "End date of the billing plan, in YYYY-MM-DD format.",
"type" : "string"
Expand Down
4 changes: 4 additions & 0 deletions json/PaymentService-v68.json
Original file line number Diff line number Diff line change
Expand Up @@ -3832,6 +3832,10 @@
"description" : "The number of the day, on which the recurring debit can happen. Should be within the same calendar month as the mandate recurring date.\n\nPossible values: 1-31 based on the `frequency`.",
"type" : "string"
},
"count" : {
"description" : "The number of transactions that can be performed within the given frequency.",
"type" : "string"
},
"endsAt" : {
"description" : "End date of the billing plan, in YYYY-MM-DD format.",
"type" : "string"
Expand Down
4 changes: 4 additions & 0 deletions yaml/PaymentService-v25.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2725,6 +2725,10 @@ components:

Possible values: 1-31 based on the `frequency`.'
type: string
count:
description: The number of transactions that can be performed within the
given frequency.
type: string
endsAt:
description: End date of the billing plan, in YYYY-MM-DD format.
type: string
Expand Down
4 changes: 4 additions & 0 deletions yaml/PaymentService-v30.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2974,6 +2974,10 @@ components:

Possible values: 1-31 based on the `frequency`.'
type: string
count:
description: The number of transactions that can be performed within the
given frequency.
type: string
endsAt:
description: End date of the billing plan, in YYYY-MM-DD format.
type: string
Expand Down
4 changes: 4 additions & 0 deletions yaml/PaymentService-v40.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3554,6 +3554,10 @@ components:

Possible values: 1-31 based on the `frequency`.'
type: string
count:
description: The number of transactions that can be performed within the
given frequency.
type: string
endsAt:
description: End date of the billing plan, in YYYY-MM-DD format.
type: string
Expand Down
4 changes: 4 additions & 0 deletions yaml/PaymentService-v46.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3574,6 +3574,10 @@ components:

Possible values: 1-31 based on the `frequency`.'
type: string
count:
description: The number of transactions that can be performed within the
given frequency.
type: string
endsAt:
description: End date of the billing plan, in YYYY-MM-DD format.
type: string
Expand Down
4 changes: 4 additions & 0 deletions yaml/PaymentService-v49.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3574,6 +3574,10 @@ components:

Possible values: 1-31 based on the `frequency`.'
type: string
count:
description: The number of transactions that can be performed within the
given frequency.
type: string
endsAt:
description: End date of the billing plan, in YYYY-MM-DD format.
type: string
Expand Down
4 changes: 4 additions & 0 deletions yaml/PaymentService-v50.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3591,6 +3591,10 @@ components:

Possible values: 1-31 based on the `frequency`.'
type: string
count:
description: The number of transactions that can be performed within the
given frequency.
type: string
endsAt:
description: End date of the billing plan, in YYYY-MM-DD format.
type: string
Expand Down
4 changes: 4 additions & 0 deletions yaml/PaymentService-v51.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3683,6 +3683,10 @@ components:

Possible values: 1-31 based on the `frequency`.'
type: string
count:
description: The number of transactions that can be performed within the
given frequency.
type: string
endsAt:
description: End date of the billing plan, in YYYY-MM-DD format.
type: string
Expand Down
4 changes: 4 additions & 0 deletions yaml/PaymentService-v52.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3683,6 +3683,10 @@ components:

Possible values: 1-31 based on the `frequency`.'
type: string
count:
description: The number of transactions that can be performed within the
given frequency.
type: string
endsAt:
description: End date of the billing plan, in YYYY-MM-DD format.
type: string
Expand Down
4 changes: 4 additions & 0 deletions yaml/PaymentService-v64.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3775,6 +3775,10 @@ components:

Possible values: 1-31 based on the `frequency`.'
type: string
count:
description: The number of transactions that can be performed within the
given frequency.
type: string
endsAt:
description: End date of the billing plan, in YYYY-MM-DD format.
type: string
Expand Down
4 changes: 4 additions & 0 deletions yaml/PaymentService-v67.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3775,6 +3775,10 @@ components:

Possible values: 1-31 based on the `frequency`.'
type: string
count:
description: The number of transactions that can be performed within the
given frequency.
type: string
endsAt:
description: End date of the billing plan, in YYYY-MM-DD format.
type: string
Expand Down
4 changes: 4 additions & 0 deletions yaml/PaymentService-v68.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3965,6 +3965,10 @@ components:

Possible values: 1-31 based on the `frequency`.'
type: string
count:
description: The number of transactions that can be performed within the
given frequency.
type: string
endsAt:
description: End date of the billing plan, in YYYY-MM-DD format.
type: string
Expand Down

0 comments on commit 17347a5

Please sign in to comment.