-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsocket.yml
1243 lines (1200 loc) · 37.1 KB
/
socket.yml
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
name: stripe-payments
description: Stripe offers payment solutions for businesses.
long_description: >
This socket covers Balance, Bank Account, Charges, Customers,
Disputes, Events, Sources and Tokens resources.
To make calls to specific endpoints, kindly refer to
https://stripe.com/docs/api
version: 0.0.3
runtime: nodejs_v8
config:
STRIPE_SECRET_KEY:
description: >-
Stripe Secret Key. To find the key, log into your Stripe account, navigate
to API
required: true
endpoints:
balance/list-all-balance:
private: true
description: >-
Returns a list of transactions that have contributed to the Stripe account
balance.
inputs:
properties:
available_on:
type: object
description: Optional parameters for filtering balance list.
long_description: >
Filters based on available_on. kindly refer to
https://stripe.com/docs/api
examples:
- |
{
gte: 1515628800
}
created:
type: object
description: Optional parameters for filtering list based on balance created.
long_description: >
Filters based on balance created. kindly refer to
https://stripe.com/docs/api
examples:
- |
{
gt: 1515628800
}
currency:
type: string
description: Optional parameters for filtering balance list.
long_description: >
Filters based on currency type. kindly refer to
https://stripe.com/docs/api
examples:
- usd
ending_before:
type: string
description: >-
Optional parameters for filtering balance list based on
ending_before.
long_description: >
A cursor for use in pagination. It defines your place in te list.
For instance, if you make a list request and receive 100 objects,
starting with obj_bar,
your subsequent call can include ending_before=obj_bar in order to
fetch the previous page of the list.
Filters based on ending_before. kindly refer to
https://stripe.com/docs/api
examples:
- obj_bar
limit:
type: integer
description: Optional parameters for limiting number of objects to return.
long_description: |
This can range between 1 and 100 items, and the default is 10 items.
kindly refer to https://stripe.com/docs/api
examples:
- 5
payout:
type: string
description: Optional parameters for automatic Stripe payouts only.
long_description: >
Only returns transactions that were payed out on the specified
payout ID.
kindly refer to https://stripe.com/docs/api
examples:
- tr_10340J2eZvKYlo2Cg42HilbB
source:
type: string
description: Optional parameters for returning the original transaction
long_description: |
Filters based on source. kindly refer to https://stripe.com/docs/api
examples:
- ch_19XJJ02eZvKYlo2CHfSUsSpl
starting_after:
type: string
description: >-
Optional parameters for filtering balance list based on
starting_after.
long_description: >
A cursor for use in pagination. starting_after is an object ID that
defines your place in the list.
For instance, if you make a list request and receive 100 objects,
ending with obj_foo,
your subsequent call can include starting_after=obj_foo in order to
fetch the next page of the list.
kindly refer to https://stripe.com/docs/api
examples:
- obj_foo
type:
type: string
description: >-
Optional parameters that only returns transactions of the given
type.
examples:
- charge
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "List of Balance.",
"statusCode": 200
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "Received unknown parameter: amount",
"statusCode": 400
}
balance/retrieve-balance:
private: true
description: >-
Retrieves current account balance, based on authentication used to make
the request.
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "Balance report.",
"statusCode": 200
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"message": "Make sure to use `GET` request method for retrieving balance."
}
balance/retrieve-balance-transaction:
private: true
description: Retrieves the balance transaction with the given ID.
inputs:
properties:
transID:
type: string
description: ID of the desired balance transaction.
long_description: >
The ID of the desired balance transaction (as found on any API
object
that affects the balance, e.g. a charge or transfer).
examples:
- txn_1BYXxzJbpxha41ttgmoeelpy
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "Balance transaction report.",
"statusCode": 200
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "No such balance transaction: txn_1BYXxzJbpxha41ttgm",
"statusCode": 404
}
charge/charges:
private: true
description: 'Create, Retrieve and Update actions for charges.'
long_description: |
This comprises of three actions for `charges` resource.
Make sure to use `POST`, `GET` and `PUT` request method for creating,
retrieving and updating charges respectively.
inputs:
properties:
chargeParameter:
type: object
description: Parameters for executing creating and updating of a charge.
long_description: >
This is needed for creating and updating a charge.
When creating a charge. Object must contain amount, currency and
source.
When updating a charge, the parameters are optional
examples:
- |
{
"chargeParameter":
{"currency": "usd",
"source": "tok_mastercard",
"amount": 500,
"capture":"false"
}
}
chargeID:
type: string
description: The identifier of the charge to be retrieved or updated.
long_description: >
Note that this is required for retrieve, update and shouldn't be
passed for create.
examples:
- ch_1BYXxnJbpxha41ttAGtgztsa
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "Charge Updated",
"statusCode": 200,
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "Invalid hash",
"statusCode": 400
}
charge/capture-charge:
private: true
description: 'Capture the payment of an existing, uncaptured, charge.'
inputs:
properties:
chargeID:
type: string
description: ID of a charge.
examples:
- ch_1BYXxnJbpxha41ttAGtgztsa
captureChargeParameter:
type: object
description: Optional parameters for capturing a charge.
examples:
- |
{ "amount": 500,
"receipt_email": "[email protected]"
}
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "Charge Captured",
"statusCode": 200,
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "Charge ch_1BYA0RJbpxha41ttZKjcsuTt has already been captured.",
"statusCode": 400
}
charge/list-all-charges:
private: true
description: Returns a list of charges previously created.
inputs:
properties:
customerID:
type: string
description: returns charges specific to this customer ID
examples:
- cus_BvilkNcCyAsOod
created:
type: object
description: Optional parameters for filtering charge list.
long_description: >-
Filters based on available_on kindly refer to
https://stripe.com/docs/api
examples:
- |
{
gt: 1515628800
}
ending_before:
type: string
description: >-
Optional parameters for filtering balance list based on
ending_before.
long_description: >
A cursor for use in pagination. It defines your place in te list.
For instance, if you make a list request and receive 100 objects,
starting with obj_bar,
your subsequent call can include ending_before=obj_bar in order to
fetch the previous page of the list.
Filters based on ending_before. kindly refer to
https://stripe.com/docs/api
examples:
- obj_bar
limit:
type: integer
description: Optional parameters for limiting number of objects to return.
long_description: |
This can range between 1 and 100 items, and the default is 10 items.
kindly refer to https://stripe.com/docs/api
examples:
- 3
source:
type: object
description: Optional parameters for filtering charge.
long_description: >-
filters list based on the source of the charge kindly refer to
https://stripe.com/docs/api
examples:
- |
{
object: "card"
}
starting_after:
type: string
description: >-
Optional parameters for filtering balance list based on
starting_after.
long_description: >
cursor for use in pagination. starting_after is an object ID that
defines your place in the list.
For instance, if you make a list request and receive 100 objects,
ending with obj_foo,
your subsequent call can include starting_after=obj_foo in order to
fetch the next page of the list.
kindly refer to https://stripe.com/docs/api
examples:
- obj_foo
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "List of Charges",
"statusCode": 200
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "Received unknown parameter: id",
"statusCode": 400
}
customers/customer:
private: true
description: 'Create, Retrieve, Update and Delete actions for customer.'
long_description: >
This comprises of four actions for `customers` resource.
Make sure to use `POST`, `GET`, `PUT` and `DELETE` request method for
creating,
retrieving, updating and deleting customers respectively.
inputs:
properties:
customerID:
type: string
description: >-
A compulsory identifier of the charge to be retrieved, updated or
deleted.
examples:
- cus_BvilkNcCyAsOod
customerParameter:
type: object
description: Optional Parameters for creating and updating customer.
examples:
- |
{
"customerParameter":
{ "account_balance": 1000,
"description": "testing things",
"email": "[email protected]"
}
}
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "Customer created successfully.",
"statusCode": 200,
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "Received unknown parameter: limit",
"statusCode": 400
}
customers/list-all-customers:
private: true
description: Returns a list of your customers.
inputs:
properties:
created:
type: object
description: Optional parameters for filtering customer's list.
long_description: >-
Filters based on available_on. kindly refer to
https://stripe.com/docs/api
examples:
- |
{
lte: 1515628800
}
email:
type: string
description: >-
Filters list based on customer's email. kindly refer to
https://stripe.com/docs/api
examples:
ending_before:
type: string
description: >-
Optional parameters for filtering balance list based on
ending_before.
long_description: >
A cursor for use in pagination. It defines your place in te list.
For instance, if you make a list request and receive 100 objects,
starting with obj_bar,
your subsequent call can include ending_before=obj_bar in order to
fetch the previous page of the list.
Filters based on ending_before. kindly refer to
https://stripe.com/docs/api
examples:
- obj_bar
limit:
type: integer
description: Optional parameters for limiting number of objects to return.
long_description: |
This can range between 1 and 100 items, and the default is 10 items.
kindly refer to https://stripe.com/docs/api
examples:
- 3
starting_after:
type: string
description: >-
Optional parameters for filtering balance list based on
starting_after.
long_description: >
cursor for use in pagination. starting_after is an object ID that
defines your place in the list.
For instance, if you make a list request and receive 100 objects,
ending with obj_foo,
your subsequent call can include starting_after=obj_foo in order to
fetch the next page of the list.
kindly refer to https://stripe.com/docs/api
examples:
- obj_foo
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "List of Customers.",
"statusCode": 200,
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "Received unknown parameter: id",
"statusCode": 400
}
disputes/close-dispute:
private: true
description: Closes dispute for a charge.
inputs:
properties:
chargeID:
disputeID:
type: string
description: ID of dispute to close.
examples:
- dp_1BXrJvJbpxha41ttpCkU6s2D
captureChargeParameter:
type: object
description: Optional parameters for capturing a charge.
examples:
- |
{ "amount": 500,
"receipt_email": "[email protected]"
}
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "Dispute closed.",
"statusCode": 200
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "No such dispute: dp_1BZD3gJbpxha41ttQMvPAnPz",
"statusCode": 404
}
disputes/dispute:
private: true
description: Retrieve and Update actions for dispute.
long_description: |
This comprises of two actions for `disputes` resource.
Make sure to use `GET` and `PUT` request method for
retrieving and updating charges respectively.
inputs:
properties:
disputeID:
type: string
description: The identifier of the dispute to retrieve or update.
examples:
- dp_1BXrJvJbpxha41ttpCkU6s2D
disputeParameter:
type: object
description: Should contain optional parameters for updating of dispute.
examples:
- |
{
"disputeParameter":
"evidence": {
"customer_name": "Anthony Johnson",
"product_description": "Comfortable cotton t-shirt",
"shipping_documentation": "file_1BXrK4Jbpxha41ttgNYLcslo"
}
}
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "Dispute retrieved successfully",
"statusCode": 200,
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "No such dispute: dp_1BZD3gJbpxha41ttQMvPAnPz",
"statusCode": 404
}
disputes/list-all-disputes:
private: true
description: Returns a list of all disputes.
inputs:
properties:
chargeID:
type: string
description: ID of a charge.
examples:
- ch_1BYXxnJbpxha41ttAGtgztsa
disputesParams:
type: object
description: >-
Optional parameters for listing disputes. kindly refer to
https://stripe.com/docs/api
examples:
- |
{
limit: 3
}
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "List of Disputes.",
"statusCode": 200
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "Received unknown parameter: id",
"statusCode": 400
}
events/list-all-events:
private: true
description: Returns a list of all events.
inputs:
properties:
eventsParams:
type: object
description: >-
Optional parameters for listing events. kindly refer to
https://stripe.com/docs/api
examples:
- |
{
limit: 3
}
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "List of Events.",
"statusCode": 200
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "Received unknown parameter: id",
"statusCode": 400
}
events/retrieve-event:
private: true
description: Closes dispute for a charge.
inputs:
properties:
eventID:
type: string
description: The identifier of the event to be retrieved.
examples:
- evt_1BYXxzJbpxha41tt0cH1164E
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "Event retrieved successfully.",
"statusCode": 200
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "No such event: evt_1BYXxzJbpxha41tt0cH",
"statusCode": 404
}
tokens/token:
private: true
description: Creates a single use token that wraps the details of a credit card.
inputs:
properties:
tokenID:
type: string
description: The ID of the desired token.
examples:
- tok_1BZKxVJbpxha41ttee6PDtyQ
tokenParams:
type: object
description: Parameters for creating token
long_description: >
Parameters provided must be either a card, customer, pii data, or
bank account to create a token.
Reference Stripe API reference documentation.
examples:
- |
{
"tokenParams":
{
"card": {
"number": 4242424242424242,
"exp_month": 12,
"exp_year": 2018,
"cvc": 123
}
}
}
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "Token created successfully.",
"statusCode": 200
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "You must supply either a card, customer, pii data, or bank account to create a token.",
"statusCode": 400
}
bank-accounts/bank-account:
private: true
description: 'Create, Retrieve, Update and Delete actions for bank account.'
long_description: >
This comprises of four actions for `bank accounts` resource.
Make sure to use `POST`, `GET`, `PUT` & `DELETE` request method for
creating,
retrieving, updating & deleting bank accounts respectively.
inputs:
properties:
customerID:
type: string
description: >-
A compulsory customer identifier of the bank account to be
retrieved, updated or deleted.
examples:
- cus_BwTBe5lcoH6QBA
bankAcctID:
type: string
description: >-
A compulsory identifier of the bank account to be retrieved, updated
or deleted.
examples:
- card_1BZKxVJbpxha41ttCbNJuOWy
bankAcctParams:
type: object
description: Addition arguments for creating and updating bank account.
examples:
- |
{
"bankAcctParams":
{
"source": "tok_1BZKxVJbpxha41ttee6PDtyQ"
}
}
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "Bank Account Retrieved",
"statusCode": 200,
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "Missing required param: source.",
"statusCode": 400
}
bank-accounts/list-all-bank-accounts:
private: true
description: Returns a list of the bank accounts belonging to a Customer.
inputs:
properties:
customerID:
type: string
description: The ID of the customer whose bank accounts will be retrieved.
examples:
- cus_BwTBe5lcoH6QBA
limit:
type: integer
description: Optional parameters for limiting number of objects to return.
long_description: |
This can range between 1 and 100 items, and the default is 10 items.
kindly refer to https://stripe.com/docs/api
examples:
- 3
ending_before:
type: string
description: >-
Optional parameters for filtering balance list based on
ending_before.
long_description: >
A cursor for use in pagination. It defines your place in te list.
For instance, if you make a list request and receive 100 objects,
starting with obj_bar,
your subsequent call can include ending_before=obj_bar in order to
fetch the previous page of the list.
Filters based on ending_before. kindly refer to
https://stripe.com/docs/api
examples:
- obj_bar
starting_after:
type: string
description: >-
Optional parameters for filtering balance list based on
starting_after.
long_description: >
cursor for use in pagination. starting_after is an object ID that
defines your place in the list.
For instance, if you make a list request and receive 100 objects,
ending with obj_foo,
your subsequent call can include starting_after=obj_foo in order to
fetch the next page of the list.
kindly refer to https://stripe.com/docs/api
examples:
- obj_foo
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "List of Bank Accounts.",
"statusCode": 200,
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "Received unknown parameter: limi",
"statusCode": 400
}
bank-accounts/verify-bank-accounts:
private: true
description: >-
Verifies the customer's bank account. This only works with real bank
account information.
inputs:
properties:
customerID:
type: string
description: The ID of the customer whose bank accounts will be verified.
examples:
- cus_BwTBe5lcoH6QBA
bankAcctID:
type: string
description: The ID of the source to be verified.
examples:
- ba_1BZD3aJbpxha41ttq4aQGcL5
bankAcctParams:
type: object
description: >-
Optional parameters for verifying bank accounts. kindly refer to
https://stripe.com/docs/api
examples:
- |
{
"bankAcctParams": {
"amounts": [32, 45]
}
}
outputs:
success:
exit_code: 200
description: Success
examples:
- |
{
"message": "Bank Account Retrieved.",
"statusCode": 200
"data": {}
}
fail:
exit_code: 400
description: Failed
examples:
- |
{
"type": "StripeInvalidRequestError",
"message": "The payment source card_1BZLlzJbpxha41ttuQ1XGBpE does not require validation.",
"statusCode": 400
}
cards/card:
private: true
description: 'Create, Retrieve, Update and Delete actions for cards.'
long_description: >
This comprises of four actions for `customers` resource.
Make sure to use `POST`, `GET`, `PUT` and `DELETE` request method for
creating,
retrieving, updating and deleting customers respectively.
inputs:
properties:
cardID:
type: string
description: 'A compulsory card identifier of to be retrieved, updated or deleted'
examples:
- card_1BZmhWJbpxha41tt0owIItGH
customerID:
type: string
description: >-
A compulsory customer identifier of the card to be retrieved,
updated or deleted.
examples:
- cus_BvilkNcCyAsOod
cardParams:
type: object
description: Parameters for creating and updating customer.
long_description: |
When creating a card. Object must contain source.
When updating a card, the parameters are optional
examples: