HTM/ovpay
4
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases 1 Wiki Activity

Compare commits

base: HTM:4f54aaf02774f719223156941edca7f1db5d98f8
Branches Tags
HTM:develop
HTM:features/OVPAY2475-Token-API
HTM:feature/OVPAY-2547
HTM:trial-implementation-Not-beheren
HTM:features/FIKO-voor-kassa
HTM:features/OVPAY1312-TP-orders-incl-vouchers
HTM:features/Edit-TP-notification
HTM:feature/OVPAY-1499
HTM:main
HTM:version/3
HTM:version/2
HTM:version/1
HTM:V1
..
compare: HTM:8fc5d3b55ecae1a9dc4ecb5d0606b55c176b7508
Branches Tags
HTM:develop
HTM:features/OVPAY2475-Token-API
HTM:feature/OVPAY-2547
HTM:trial-implementation-Not-beheren
HTM:features/FIKO-voor-kassa
HTM:features/OVPAY1312-TP-orders-incl-vouchers
HTM:features/Edit-TP-notification
HTM:feature/OVPAY-1499
HTM:main
HTM:version/3
HTM:version/2
HTM:version/1
HTM:V1

No commits in common. "4f54aaf02774f719223156941edca7f1db5d98f8" and "8fc5d3b55ecae1a9dc4ecb5d0606b55c176b7508" have entirely different histories.
4f54aaf027 ... 8fc5d3b55e

1 changed files with 14 additions and 43 deletions
Show Stats Expand all files Collapse all files

57
src/openapi/claims/claims-forms.yaml
View File

@ -17,10 +17,10 @@ paths:
description: >
Create a claim by sending a JSON as specified in the schema. By
specifying the chipcardnumber under 'chipkaart',
a claim for OV chipcard will be sent to the OVC API. If no
chipcardnumber is specified under 'chipkaart', a claim for EMV/OV-pas is sent
to Mendix, where it can be handled according to the fields present
(serviceRefId + totaalbedrag or ovPasNumber + verificationCode)
a claim for OV chipcard will be send to the OVC API. If no
chipcardnumber is specified under 'chipkaart', a claim for EMV is send
to mendix.
parameters: []
requestBody:
content:
@ -47,6 +47,8 @@ paths:
toelichting: string
lijn: '1'
vervoertype: '1'
serviceRefId: '1'
Totaalbedrag: 0
EMV:
value:
aankomsthalte: '1'
@ -65,28 +67,8 @@ paths:
toelichting: string
lijn: '1'
vervoertype: '1'
serviceRefId: 'NLOV1234567ABCDEFG'
totaalbedrag: 3.14
OV-pas:
value:
aankomsthalte: '1'
instapdatum: '2024-03-06T15:20:44.549Z'
instaptijd: '2024-03-06T15:20:44.549Z'
ingecheckt: true
uitgecheckt: true
afgeschrevenbedrag: 0
vertrekhalte: string
korting: true
iban: '1234123412341234'
naam: string
emailadres: user@example.com
uitstaptijd: '2024-03-06T15:20:44.549Z'
verwachtbedrag: 0
toelichting: string
lijn: '1'
vervoertype: '1'
ovPasNumber: '63AW974'
verificationCode: '2FQ8'
serviceRefId: '1'
Totaalbedrag: 0
responses:
'200':
description: ok
@ -121,19 +103,18 @@ paths:
examples:
EMV:
value:
emailAddress: 'stasjo@htm.nl'
emailAddress: 'j.beek@htm.nl'
orderNumber: 'ORD1000046'
serviceReferenceId: 'NLOVA5BCD124H3Z21X'
amount: 2305
iban: 'NL98INGB0003856625'
orderDate: '2025-01-13'
productName: 'HTM 20% korting'
OV-pas:
OVpas:
value:
emailAddress: 'stasjo@htm.nl'
emailAddress: 'j.beek@htm.nl'
orderNumber: 'ORD1000046'
ovpasNumber: '63AW974'
verificationCode: '2FQ8'
iban: 'NL98INGB0003856625'
orderDate: '2025-01-13'
productName: 'HTM 20% korting'
@ -200,7 +181,7 @@ components:
iban:
type: string
description: String of length between 15 en 32 characters
example: NL98INGB0003856625
example: '1234123412341234'
naam:
type: string
emailadres:
@ -220,16 +201,9 @@ components:
type: string
serviceRefId:
type: string
example: NLOV1234567ABCDEFG
totaalbedrag:
Totaalbedrag:
type: number
format: float
ovPasNumber:
type: string
example: 63AW974
verificationCode:
type: string
example: 2FQ8
refundsEntity:
required:
- emailAddress
@ -239,7 +213,7 @@ components:
emailAddress:
type: string
format: email
example: stasjo@htm.nl
example: j.beek@htm.nl
orderNumber:
type: string
example: ORD1000046
@ -252,9 +226,6 @@ components:
ovpasNumber:
type: string
example: 63AW974
verificationCode:
type: string
example: 2FQ8
iban:
type: string
example: NL00RABO000001337