-
Notifications
You must be signed in to change notification settings - Fork 5
/
openapi.yaml
3219 lines (3089 loc) · 104 KB
/
openapi.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
openapi: 3.0.3
info:
title: Real-time payments, everywhere.
description: >
Join the real-time revolution! Give your customers a faster, easier and
safer way to pay. Volt has developed a REST API for merchants, allowing you
to offer the option to use Open Banking payments on your online checkout.
## NEW : API idempotency
We have introduced support for idempotency on the POST endpoints in the Volt
Connect endpoints of the API. The idea of idempotency is to avoid unwanted
duplication should a request to our API fail and need to be retried.
Using a unique idempotency key for each POST request, it is possible to
safely retry the same call multiple times with the guarantee that it will
only be actioned once.
### Endpoints supporting idempotency
If an endpoint supports idempotent processing, we'll indicate this in the
header documentation for that endpoint.
### Using an idempotency key
Using the idempotency key is optional. If you would like to use it to help
prevent duplicates in your POST requests, simply include the header
```idempotency-key: <key>``` - where ```<key>``` is a unique identifier for
the message. We recommend using a **UUID** for the key, however you may use
any other unique identifier you choose.
### Retries
If the request times out or you don't receive a response for any other
reason, you may safely retry it using the same payload and headers. Use the
same key for the retried attempt.
### Preventing duplicates
If we have already processed the request and you send a request using the
same idempotency key, it will fail with an error, returning an HTTP code of
```409``` Conflict.
### Exponential backoff for retries
You should adopt an exponential backoff strategy when retrying requests
using the same idempotency key. For example, retry 1 second later then, if
it fails again, 2 seconds later, 4 seconds later etc.
version: 2024.04.11
x-konfig-ignore:
object-with-no-properties: true
potential-incorrect-type: true
servers:
- description: >
Sandbox server - start here and make test payments through our model
banks.
url: https://api.sandbox.volt.io
- description: >
Production server - when you're ready to make live payments, connect to
Volt's banking network.
url: https://api.volt.io
tags:
- name: Reporting
- name: Payments
- name: Payouts (Connect)
- name: Refunds (Connect)
- name: Authenticating with the API
- name: Banks and financial institutions
- name: Matchmeter
paths:
/oauth:
post:
tags:
- Authenticating with the API
summary: oAuth2 password authentication
operationId: AuthenticatingWithTheApi_usingOAuth2Password
description: >
We use the industry-standard oAuth2 authentication to secure our API.
### Information you'll need
- Your **Client ID** and **Client Secret** (from the application you
created in Fuzebox)
- Your **API username** and **password** (from the merchant credentials
section in Fuzebox)
Step-by-step instructions on how to authenticate are available in our
[product guides](https://docs.volt.io/gateway/authentication/]) area.
requestBody:
content:
application/x-www-form-urlencoded:
schema:
$ref: >-
#/components/schemas/AuthenticatingWithTheApiUsingOAuth2PasswordRequest
required: true
responses:
'200':
description: |
**OK** - Successful login attempt, returning an access token
content:
application/json:
schema:
$ref: >-
#/components/schemas/AuthenticatingWithTheApiUsingOAuth2PasswordResponse
'401':
$ref: '#/components/responses/401'
x-stoplight:
id: crymw4j35sz4f
/banks/{id}:
get:
tags:
- Banks and financial institutions
summary: Bank details
operationId: BanksAndFinancialInstitutions_getDetails
description: View details about a single bank or financial institution
parameters:
- name: id
in: path
required: true
example: 662384a0-9734-4556-a8bd-3f1e774e2a3c
schema:
description: UUID of the Bank
type: string
responses:
'200':
description: Details of bank or financial institution
content:
application/json:
schema:
$ref: '#/components/schemas/bank_full'
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
'404':
$ref: '#/components/responses/404'
x-stoplight:
id: gggi6h8jroy0q
/v2/payments:
post:
tags:
- Payments
summary: New payment request
operationId: Payments_submitDetails
description: >
The first step is to submit the details of the payment you'd like to
initiate. We'll validate that all the required data is supplied and
that it's a payment that Volt can support.
Step-by-step instructions for payment initiation are available in our
[product guides](https://docs.volt.io/gateway/hosted/) area.
requestBody:
description: Details of the payment you'd like to initiate
content:
application/json:
schema:
$ref: '#/components/schemas/payment'
required: false
responses:
'201':
description: >
**Created** - The payment request was validated and accepted and a
payment ID returned
content:
application/json:
schema:
$ref: '#/components/schemas/PaymentsSubmitDetailsResponse'
'400':
$ref: '#/components/responses/400'
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
x-stoplight:
id: 6rh252bydol2e
x-internal: false
/dropin:
post:
tags:
- Payments
summary: New Embedded checkout
operationId: Payments_initiateEmbeddedCheckout
description: >
The first step is to submit the details of the payment you'd like to
initiate. We'll validate that all the required data is supplied and that
it's a payment that Volt can support.v2.
Step-by-step instructions for creating Embedded Checkout are available
in our [product
guides](https://docs.volt.io/gateway/embedded-checkout-v1/embedded-checkout-v2/)
area.
requestBody:
description: Details of the payment you'd like to initiate
content:
application/json:
schema:
$ref: '#/components/schemas/PaymentsInitiateEmbeddedCheckoutRequest'
required: false
responses:
'201':
description: >
**Created** - The payment request was validated and accepted and a
payment ID returned
content:
application/json:
schema:
$ref: '#/components/schemas/PaymentsInitiateEmbeddedCheckoutResponse'
'400':
$ref: '#/components/responses/400'
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
x-stoplight:
id: 7a5nksmppj3ar
/payments:
get:
tags:
- Payments
summary: List payments
operationId: Payments_getList
description: >-
Reporting API available to fetch list of payments based on specific
selection criteria
parameters:
- description: UUID of the Payment
in: query
name: id
required: false
example: 662384a0-9734-4556-a8bd-3f1e774e2a3c
schema:
type: string
format: uuid
- description: UUID of the Bank
in: query
name: bank
required: false
example: 662384a0-9734-4556-a8bd-3f1e774e2a3c
schema:
type: string
format: uuid
- description: >-
3-letter currency code - See [ISO 4217 - Currency
codes](https://www.iso.org/iso-4217-currency-codes.html)
in: query
name: currency
example: EUR
required: false
schema:
type: string
- description: The amount of the transaction in 1/100 units (pence, cents etc)
name: amount
in: query
example: 12345
schema:
type: integer
- description: The transaction type (these are predefined)
name: type
in: query
example: OTHER
schema:
type: string
enum:
- BILL
- GOODS
- PERSON_TO_PERSON
- OTHER
- SERVICES
- description: Unique reference for the payment
name: uniqueReference
in: query
example: sale123456
schema:
type: string
- description: The current status of the payment
name: status
in: query
example: REQUESTED
schema:
type: string
- $ref: '#/components/parameters/page'
- $ref: '#/components/parameters/limit'
responses:
'200':
description: |
**OK** - All payments corresponding to specified filters
content:
application/json:
schema:
$ref: '#/components/schemas/PaymentsGetListResponse'
example:
- id: ed2f2418-3009-48e0-9a43-051e5c3ee5b6
active: true
createdAt: '2023-02-16T09:42:20+00:00'
currency:
id: GBP
name: POUND STERLING
decimal: 2
active: true
amount: 1
type: BILL
account:
id: 66683afe-7dc0-4939-8dab-4a3d657b2b91
active: true
createdAt: '2021-04-29T08:15:42+00:00'
currency:
id: GBPX
name: POUND STERLING
decimal: 2
active: true
country:
id: GB
name: United Kingdom
bank:
id: e822a93c-72d4-4de1-8bcc-2381370c5437
name: Ulster Bank (UK)
country:
id: GBX
name: United Kingdom
officialName: Ulster Bank (UK)
localName: null
branchName: Ulster Bank (UK)
shortBranchName: null
createdAt: '2022-06-01T13:45:14+00:00'
active: true
logo: https://cdn.sandbox.volt.io/banks/logos/default.png
icon: https://cdn.sandbox.volt.io/banks/icons/default.png
uniqueReference: AJmEznH3kLVT2mpoqK
status: RECEIVED
statusUpdates:
- createdAt: '2023-02-16T09:42:37+00:00'
newStatus: APPROVED_BY_RISK
- createdAt: '2023-02-16T09:42:37+00:00'
newStatus: BANK_REDIRECT
- createdAt: '2023-02-16T09:43:10+00:00'
newStatus: AUTHORISED_BY_USER
- createdAt: '2023-02-16T09:43:11+00:00'
newStatus: COMPLETED
- createdAt: '2023-02-16T09:45:01+00:00'
newStatus: RECEIVED
beneficiary:
id: cc9a9f87-7be9-4aae-928d-a27b9c3b689c
customerId: e6707f41-5f2a-4a39-8338-084fb3a8e19b
accountIdentifications:
- type: sortCode
value: '123456'
- type: accountName
value: Test CM account
- type: accountNumber
value: '12345678'
country:
id: GBX
name: United Kingdom
transferType: Faster Payments Scheme
pblValidityPeriod: null
sender:
name: null
email: null
ip: null
deviceFingerprint: c1fc9f277826d16825940603196ab037
voltConnect:
accountName: Jane Doe
accountNumber: null
sortCode: null
- id: 729771f6-37a3-4635-836f-566b60b217a8
active: true
createdAt: '2023-02-16T09:32:24+00:00'
currency:
id: GBPX
name: POUND STERLING
decimal: 2
active: true
amount: 1
type: BILL
account:
id: 66683afe-7dc0-4939-8dab-4a3d657b2b91X
active: true
createdAt: '2021-04-29T08:15:42+00:00'
currency:
id: GBPX
name: POUND STERLING
decimal: 2
active: true
country:
id: GBX
name: United Kingdom
bank:
id: c2a44111-03df-475a-9800-e7ce6bbaa0b7
name: Natwest Bank Sandbox
country:
id: GBX
name: United Kingdom
officialName: Natwest Bank Sandbox
localName: null
branchName: Natwest Bank Sandbox
shortBranchName: null
createdAt: '2021-08-10T14:34:02+00:00'
active: true
logo: https://cdn.sandbox.volt.io/banks/logos/default.png
icon: https://cdn.sandbox.volt.io/banks/icons/default.png
uniqueReference: 6eSCeNp4Pd0CRruSPt
status: RECEIVED
statusUpdates:
- createdAt: '2023-02-16T09:32:34+00:00'
newStatus: APPROVED_BY_RISK
- createdAt: '2023-02-16T09:32:34+00:00'
newStatus: BANK_REDIRECT
- createdAt: '2023-02-16T09:33:23+00:00'
newStatus: AUTHORISED_BY_USER
- createdAt: '2023-02-16T09:33:24+00:00'
newStatus: COMPLETED
- createdAt: '2023-02-16T09:35:02+00:00'
newStatus: RECEIVED
beneficiary:
id: cc9a9f87-7be9-4aae-928d-a27b9c3b689cX
customerId: e6707f41-5f2a-4a39-8338-084fb3a8e19b
accountIdentifications:
- type: sortCode
value: '123456'
- type: accountName
value: Test CM account
- type: accountNumber
value: '12345678'
country:
id: GBX
name: United Kingdom
transferType: Faster Payments Scheme
pblValidityPeriod: null
sender:
name: null
email: null
ip: null
deviceFingerprint: c1fc9f277826d16825940603196ab037
voltConnect:
accountName: Jane Doe
accountNumber: null
sortCode: null
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
x-stoplight:
id: w36v7atgt3lul
/payments/{id}:
get:
tags:
- Payments
summary: Payment details
operationId: Payments_getDetails
description: >
Returns the full details of an existing payment that you've created
througn the POST /payments endpoint. Simply supply the ```id``` of the
payment we returned when the payment was created.
You can retrieve a filterable list of payments through the ```GET
/payments``` endpoint.
parameters:
- description: ID of the payment
name: id
example: 93b85f3c-76eb-4316-b1ae-f3370ddc59bc
in: path
required: true
schema:
type: string
format: uuid
responses:
'200':
description: |
**OK** - Payment details for the ID specified
content:
application/json:
schema:
$ref: '#/components/schemas/payment_full'
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
'404':
$ref: '#/components/responses/404'
x-stoplight:
id: xyws709wfnvzh
/payouts/beneficiaries:
get:
tags:
- Payouts (Connect)
summary: Eligible beneficiaries list
operationId: PayoutsConnect_eligibleBeneficiariesList
description: >
**Payouts are only available when using Volt Connect**
For regulatory purposes, it's a closed-loop payout system, meaning you
may only payout funds to a person or organisation you've previously
received money from using Volt Connect.
This endpoint will return a list of beneficiaries you are allowed send
payouts to.
### Usage
The list is paginated by default.
### More information
Full details on payouts can be found in our comprehensive integration
guides.
parameters:
- description: Name of the beneficiary you'd like to send a payout to
name: name
in: query
schema:
type: string
- description: >-
Domestic account number for the beneficiary you'd like to send a
payout to
name: accountNumber
in: query
schema:
type: string
- description: iban for the beneficiary you'd like to send a payout to
name: iban
in: query
schema:
type: string
- $ref: '#/components/parameters/page'
- $ref: '#/components/parameters/limit'
responses:
'200':
description: |
**OK** - A paginated list of eligible beneficiaries.
content:
application/json:
schema:
$ref: >-
#/components/schemas/PayoutsConnectEligibleBeneficiariesListResponse
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
externalDocs:
description: |
Integration guide: Payouts
url: https://docs.volt.io/connect/payouts/
x-stoplight:
id: wazr6t5n0gyap
/payouts:
post:
tags:
- Payouts (Connect)
summary: New payout request
operationId: PayoutsConnect_createRequest
description: >
**Payouts are only available when using Volt Connect**
This will create a payout request to send funds from your Connect
account to a beneficiary. For regulatory purposes, it's a closed-loop
payout system, meaning you may only payout funds to a person or
organisation you've previously received money from using Volt Connect.
### Usage
Pass the details of the payout you'd like to make in the body of the
request.
### Approval
Payouts don't require approval if you create them using the API. If you
need to review payouts before sending, this workflow should take place
on your own system before you call this endpoint.
### More information
Full details on payouts can be found in our comprehensive integration
guides.
parameters:
- description: Recommended to avoid duplicate payout requests
in: header
name: idempotency-key
schema:
type: string
format: uuid
- description: Optional - applicable if Volt is your Connect partner
schema:
type: string
in: header
name: X-JWS-Header
requestBody:
description: Details of the payout you'd like to create
content:
application/json:
schema:
$ref: '#/components/schemas/payout_request'
required: false
responses:
'201':
description: >
**Created** - The payout request was validated and accepted and a
payout ID returned.
content:
application/json:
schema:
$ref: '#/components/schemas/PayoutsConnectCreateRequestResponse'
'400':
description: >
**Bad request** - The request could not be processed due to one or
more errors. If the exception message does not provide enough
information, please contact merchant support for further details.
content:
application/json:
schema:
$ref: '#/components/schemas/PayoutsConnectCreateRequest400Response'
'401':
$ref: '#/components/responses/401'
'403':
description: >
**Forbidden** - Although your credentials are correct, your access
to payout functionality on the API has been disabled or restricted.
If the exception message does not provide enough information, please
contact merchant support for further details.
content:
application/json:
schema:
$ref: '#/components/schemas/PayoutsConnectCreateRequest403Response'
'409':
$ref: '#/components/responses/409'
'422':
description: >
**Unprocessable Entity** - The payout request could not be completed
due to a problem with the beneficiary you're trying to send to. If
the exception message does not provide enough information, please
contact merchant support for further details.
content:
application/json:
schema:
$ref: '#/components/schemas/PayoutsConnectCreateRequest422Response'
externalDocs:
description: |
Integration guide: Payouts
url: https://docs.volt.io/connect/payouts/
x-stoplight:
id: kqsjgtn9xnn2p
get:
tags:
- Payouts (Connect)
summary: Payout list
operationId: PayoutsConnect_getList
description: >
**Payouts are only available when using Volt Connect**
This will return a list of all existing payouts.
### Usage
The list is paginated by default and can be filtered using the
parameters shown in the request section below.
### More information
Full details on payouts can be found in our comprehensive integration
guides.
parameters:
- $ref: '#/components/parameters/page'
- $ref: '#/components/parameters/limit'
responses:
'200':
description: |
**OK** - A paginated list of payouts.
content:
application/json:
schema:
$ref: '#/components/schemas/payout_list'
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
externalDocs:
description: |
Integration guide: Payouts
url: https://docs.volt.io/connect/payouts/
x-stoplight:
id: 8xnw41z5ucb59
/payouts/{id}:
get:
tags:
- Payouts (Connect)
summary: Payout details
operationId: PayoutsConnect_getDetails
description: >
**Payouts are only available when using Volt Connect**
This will return details of the selected payout, with approval update
history.
### Usage
Pass the **id** of the payout as part of the URL.
### More information
Full details on payouts can be found in our comprehensive integration
guides.
parameters:
- description: ID of the payout
name: id
example: efffed42-40f7-4bd2-840d-908aae9a33ad
in: path
required: true
schema:
type: string
responses:
'200':
description: |
**OK** - Details of the selected payout
content:
application/json:
schema:
$ref: '#/components/schemas/PayoutsConnectGetDetailsResponse'
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
externalDocs:
description: |
Integration guide: Payouts
url: https://docs.volt.io/connect/payouts/
x-stoplight:
id: 86b830u6vxgp6
/payments/{id}/refund-details:
get:
tags:
- Refunds (Connect)
summary: Check refund eligibility
operationId: RefundsConnect_checkEligibility
description: >
**Refunds are only available when using Volt Connect**
### Usage
Pass the **id** of the existing payment in the URL to check whether this
payment is eligible for a refund.
### More information
Full details on how to request refunds, with full details of
notifications you can expect, can be found in our comprehensive
integration guides.
parameters:
- description: ID of the refund
name: id
example: 93b85f3c-76eb-4316-b1ae-f3370ddc59bc
in: path
required: true
schema:
type: string
format: uuid
responses:
'200':
description: All payments details for specified filters
content:
application/json:
schema:
$ref: '#/components/schemas/RefundsConnectCheckEligibilityResponse'
'400':
$ref: '#/components/responses/400'
'401':
$ref: '#/components/responses/401'
'403':
$ref: '#/components/responses/403'
externalDocs:
description: |
Integration guide: Refunds
url: https://docs.volt.io/connect/refunds-via-api/
x-stoplight:
id: no8qiwijobr83
/payments/{id}/request-refund:
post:
tags:
- Refunds (Connect)
summary: New refund request
operationId: RefundsConnect_createRequest
description: >
**Refunds are only available when using Volt Connect**
### Usage
Pass the **id** of the existing payment in the URL and the amount and
reference for the refund in the body of the request.
### Checking eligibility before requesting a refund
You can get the eligibility for a refund using GET
/payments/{id}/refund-details
### More information
Full details on how to use refunds, with details of notifications you
can expect, can be found in our comprehensive integration guides.
parameters:
- description: Optional - but recommended - to avoid duplicate refund requests
in: header
name: idempotency-key
schema:
type: string
format: uuid
- description: ID of the payment
name: id
example: 93b85f3c-76eb-4316-b1ae-f3370ddc59bc
in: path
required: true
schema:
type: string
- description: Optional - applicable if Volt is your Connect partner
schema:
type: string
in: header
name: X-JWS-Header
requestBody:
description: Details of the refund you'd like to request for this payment
content:
application/json:
schema:
$ref: '#/components/schemas/refund_request'
responses:
'201':
description: |
**Created** - The refund request was validated and accepted.
content:
application/json:
schema:
$ref: '#/components/schemas/RefundsConnectCreateRequestResponse'
'400':
$ref: '#/components/responses/400'
'401':
$ref: '#/components/responses/401'
'403':
description: >
**Not authorised** - Although your credentials are correct, your
access to this section of the API has been disabled or limited.
Subsequent requests to this endpoint (even with valid data) will not
be processed.
content:
application/json:
schema:
$ref: '#/components/schemas/RefundsConnectCreateRequest403Response'
'409':
$ref: '#/components/responses/409'
'422':
description: >
**Unprocessable Entity** - The payout request could not be completed
due to a problem with the beneficiary you're trying to send to. If
the exception message does not provide enough information, please
contact merchant support for further details.
content:
application/json:
schema:
$ref: '#/components/schemas/RefundsConnectCreateRequest422Response'
externalDocs:
description: |
Integration guide: Refunds via the API
url: https://docs.volt.io/connect/refunds-via-api/
x-stoplight:
id: imxi4gqo57xyy
/reports/payments:
parameters: []
post:
tags:
- Reporting
summary: Create payment report
operationId: Reporting_createPaymentReport
description: >
This endpoint allows you to request a payment report for a specific
period. Once requested, your report will be generated asynchronously
and available at the ```/reports/id/download endpoint``` as a CSV file
once it's been generated. Check on the availability status of your
report using the ```/reports/{id}``` endpoint.
The ```startDate``` and ```endDate``` may be a maximum of **92 days**
apart, so you can generate reports containing 3 months data.
If you supply a ```customerId``` for any merchant within your customer
hierarchy, only that merchant's data will be returned.
If a ```customer ID``` is **not** provided, the report will contain data
for all merchants within your customer hierarchy.
requestBody:
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/ReportingCreatePaymentReportRequest'
examples:
Example with customerId provided:
value:
startDate: '2019-08-24T14:15:22+00:00'
endDate: '2019-08-24T14:15:22+00:00'
customerId: 87d8e330-2878-4742-a86f-dbbb3bf522ac
Example without customerId:
value:
startDate: '2019-08-24T14:15:22+00:00'
endDate: '2019-08-24T14:15:22+00:00'
responses:
'201':
description: Created
content:
application/json:
schema:
$ref: '#/components/schemas/report_requested'
'400':
description: |
**Bad Request** - For example, when invalid JSON was provided.
content:
application/json:
schema:
$ref: '#/components/schemas/ReportingCreatePaymentReportResponse'
examples:
Bad request:
value:
exception:
code: 400
message: Bad Request
Validation error:
value:
exception:
code: 400
message: Validation exception
errorList:
- property: fieldName
message: Detailed error for that field
'422':
$ref: '#/components/responses/422'
'429':
description: >
**Too Many Requests** - This may occur when you have requested more
than 5 reports to be generated at the same time.
content:
application/json:
schema:
$ref: '#/components/schemas/ReportingCreatePaymentReport429Response'
/reports/connect/{bankAccountId}:
parameters:
- description: Connect bank account ID that you're requesting report for
schema:
type: string
name: bankAccountId
in: path
required: true
post:
tags:
- Reporting
summary: Create Connect report
operationId: Reporting_createConnectReport
description: >
This endpoint allows you to request a Connect report for a selected
```bankAccountId``` and specific period. Once requested, your report
will be generated asynchronously and available at the
```/reports/id/download endpoint``` as a CSV file once it's been
generated. Check on the availability status of your report using the
```/reports/{id}``` endpoint.
The ```startDate``` and ```endDate``` may be a maximum of **92 days**
apart, so you can generate reports containing 3 months data.
requestBody:
description: ''