Skip to content

Commit

Permalink
spec release
Browse files Browse the repository at this point in the history
  • Loading branch information
Adyen Automation committed Dec 11, 2023
1 parent 2228716 commit 35f2c0a
Show file tree
Hide file tree
Showing 62 changed files with 0 additions and 645 deletions.
5 changes: 0 additions & 5 deletions json/BinLookupService-v40.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,6 @@
"url" : "https://github.com/Adyen/adyen-openapi"
}
},
"x-groups" : [
"General"
],
"tags" : [
{
"name" : "General"
Expand All @@ -34,7 +31,6 @@
"description" : "Verifies whether 3D Secure is available for the specified BIN or card brand. For 3D Secure 2, this endpoint also returns device fingerprinting keys.\n\nFor more information, refer to [3D Secure 2](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).",
"x-addedInVersion" : "1",
"operationId" : "post-get3dsAvailability",
"x-groupName" : "General",
"x-sortIndex" : 0,
"x-methodName" : "get3dsAvailability",
"security" : [
Expand Down Expand Up @@ -143,7 +139,6 @@
"summary" : "Get a fees cost estimate",
"description" : ">This API is available only for merchants operating in Australia, the EU, and the UK.\n\nUse the Adyen Cost Estimation API to pre-calculate interchange and scheme fee costs. Knowing these costs prior actual payment authorisation gives you an opportunity to charge those costs to the cardholder, if necessary.\n\nTo retrieve this information, make the call to the `/getCostEstimate` endpoint. The response to this call contains the amount of the interchange and scheme fees charged by the network for this transaction, and also which surcharging policy is possible (based on current regulations).\n\n> Since not all information is known in advance (for example, if the cardholder will successfully authenticate via 3D Secure or if you also plan to provide additional Level 2/3 data), the returned amounts are based on a set of assumption criteria you define in the `assumptions` parameter.",
"operationId" : "post-getCostEstimate",
"x-groupName" : "General",
"x-sortIndex" : 0,
"x-methodName" : "getCostEstimate",
"security" : [
Expand Down
5 changes: 0 additions & 5 deletions json/BinLookupService-v50.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,6 @@
"url" : "https://github.com/Adyen/adyen-openapi"
}
},
"x-groups" : [
"General"
],
"tags" : [
{
"name" : "General"
Expand All @@ -34,7 +31,6 @@
"description" : "Verifies whether 3D Secure is available for the specified BIN or card brand. For 3D Secure 2, this endpoint also returns device fingerprinting keys.\n\nFor more information, refer to [3D Secure 2](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).",
"x-addedInVersion" : "1",
"operationId" : "post-get3dsAvailability",
"x-groupName" : "General",
"x-sortIndex" : 0,
"x-methodName" : "get3dsAvailability",
"security" : [
Expand Down Expand Up @@ -143,7 +139,6 @@
"summary" : "Get a fees cost estimate",
"description" : ">This API is available only for merchants operating in Australia, the EU, and the UK.\n\nUse the Adyen Cost Estimation API to pre-calculate interchange and scheme fee costs. Knowing these costs prior actual payment authorisation gives you an opportunity to charge those costs to the cardholder, if necessary.\n\nTo retrieve this information, make the call to the `/getCostEstimate` endpoint. The response to this call contains the amount of the interchange and scheme fees charged by the network for this transaction, and also which surcharging policy is possible (based on current regulations).\n\n> Since not all information is known in advance (for example, if the cardholder will successfully authenticate via 3D Secure or if you also plan to provide additional Level 2/3 data), the returned amounts are based on a set of assumption criteria you define in the `assumptions` parameter.",
"operationId" : "post-getCostEstimate",
"x-groupName" : "General",
"x-sortIndex" : 0,
"x-methodName" : "getCostEstimate",
"security" : [
Expand Down
5 changes: 0 additions & 5 deletions json/BinLookupService-v52.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,6 @@
"url" : "https://github.com/Adyen/adyen-openapi"
}
},
"x-groups" : [
"General"
],
"tags" : [
{
"name" : "General"
Expand All @@ -34,7 +31,6 @@
"description" : "Verifies whether 3D Secure is available for the specified BIN or card brand. For 3D Secure 2, this endpoint also returns device fingerprinting keys.\n\nFor more information, refer to [3D Secure 2](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).",
"x-addedInVersion" : "1",
"operationId" : "post-get3dsAvailability",
"x-groupName" : "General",
"x-sortIndex" : 0,
"x-methodName" : "get3dsAvailability",
"security" : [
Expand Down Expand Up @@ -143,7 +139,6 @@
"summary" : "Get a fees cost estimate",
"description" : ">This API is available only for merchants operating in Australia, the EU, and the UK.\n\nUse the Adyen Cost Estimation API to pre-calculate interchange and scheme fee costs. Knowing these costs prior actual payment authorisation gives you an opportunity to charge those costs to the cardholder, if necessary.\n\nTo retrieve this information, make the call to the `/getCostEstimate` endpoint. The response to this call contains the amount of the interchange and scheme fees charged by the network for this transaction, and also which surcharging policy is possible (based on current regulations).\n\n> Since not all information is known in advance (for example, if the cardholder will successfully authenticate via 3D Secure or if you also plan to provide additional Level 2/3 data), the returned amounts are based on a set of assumption criteria you define in the `assumptions` parameter.",
"operationId" : "post-getCostEstimate",
"x-groupName" : "General",
"x-sortIndex" : 0,
"x-methodName" : "getCostEstimate",
"security" : [
Expand Down
5 changes: 0 additions & 5 deletions json/BinLookupService-v53.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,6 @@
"url" : "https://github.com/Adyen/adyen-openapi"
}
},
"x-groups" : [
"General"
],
"tags" : [
{
"name" : "General"
Expand All @@ -34,7 +31,6 @@
"description" : "Verifies whether 3D Secure is available for the specified BIN or card brand. For 3D Secure 2, this endpoint also returns device fingerprinting keys.\n\nFor more information, refer to [3D Secure 2](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).",
"x-addedInVersion" : "1",
"operationId" : "post-get3dsAvailability",
"x-groupName" : "General",
"x-sortIndex" : 0,
"x-methodName" : "get3dsAvailability",
"security" : [
Expand Down Expand Up @@ -143,7 +139,6 @@
"summary" : "Get a fees cost estimate",
"description" : ">This API is available only for merchants operating in Australia, the EU, and the UK.\n\nUse the Adyen Cost Estimation API to pre-calculate interchange and scheme fee costs. Knowing these costs prior actual payment authorisation gives you an opportunity to charge those costs to the cardholder, if necessary.\n\nTo retrieve this information, make the call to the `/getCostEstimate` endpoint. The response to this call contains the amount of the interchange and scheme fees charged by the network for this transaction, and also which surcharging policy is possible (based on current regulations).\n\n> Since not all information is known in advance (for example, if the cardholder will successfully authenticate via 3D Secure or if you also plan to provide additional Level 2/3 data), the returned amounts are based on a set of assumption criteria you define in the `assumptions` parameter.",
"operationId" : "post-getCostEstimate",
"x-groupName" : "General",
"x-sortIndex" : 0,
"x-methodName" : "getCostEstimate",
"security" : [
Expand Down
5 changes: 0 additions & 5 deletions json/BinLookupService-v54.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,6 @@
"url" : "https://github.com/Adyen/adyen-openapi"
}
},
"x-groups" : [
"General"
],
"tags" : [
{
"name" : "General"
Expand All @@ -34,7 +31,6 @@
"description" : "Verifies whether 3D Secure is available for the specified BIN or card brand. For 3D Secure 2, this endpoint also returns device fingerprinting keys.\n\nFor more information, refer to [3D Secure 2](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).",
"x-addedInVersion" : "1",
"operationId" : "post-get3dsAvailability",
"x-groupName" : "General",
"x-sortIndex" : 0,
"x-methodName" : "get3dsAvailability",
"security" : [
Expand Down Expand Up @@ -143,7 +139,6 @@
"summary" : "Get a fees cost estimate",
"description" : ">This API is available only for merchants operating in Australia, the EU, and the UK.\n\nUse the Adyen Cost Estimation API to pre-calculate interchange and scheme fee costs. Knowing these costs prior actual payment authorisation gives you an opportunity to charge those costs to the cardholder, if necessary.\n\nTo retrieve this information, make the call to the `/getCostEstimate` endpoint. The response to this call contains the amount of the interchange and scheme fees charged by the network for this transaction, and also which surcharging policy is possible (based on current regulations).\n\n> Since not all information is known in advance (for example, if the cardholder will successfully authenticate via 3D Secure or if you also plan to provide additional Level 2/3 data), the returned amounts are based on a set of assumption criteria you define in the `assumptions` parameter.",
"operationId" : "post-getCostEstimate",
"x-groupName" : "General",
"x-sortIndex" : 0,
"x-methodName" : "getCostEstimate",
"security" : [
Expand Down
4 changes: 0 additions & 4 deletions json/DataProtectionService-v1.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,6 @@
"url" : "https://github.com/Adyen/adyen-openapi"
}
},
"x-groups" : [
"General"
],
"tags" : [
{
"name" : "General"
Expand All @@ -33,7 +30,6 @@
"summary" : "Submit a Subject Erasure Request.",
"description" : "Sends the PSP reference containing the shopper data that should be deleted.",
"operationId" : "post-requestSubjectErasure",
"x-groupName" : "General",
"x-sortIndex" : 0,
"x-methodName" : "requestSubjectErasure",
"security" : [
Expand Down
11 changes: 0 additions & 11 deletions json/PaymentService-v25.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,10 +16,6 @@
"url" : "https://github.com/Adyen/adyen-openapi"
}
},
"x-groups" : [
"Payments",
"Modifications"
],
"tags" : [
{
"name" : "Payments"
Expand All @@ -37,7 +33,6 @@
"summary" : "Create an authorisation",
"description" : "Creates a payment with a unique reference (`pspReference`) and attempts to obtain an authorisation hold. For cards, this amount can be captured or cancelled later. Non-card payment methods typically don't support this and will automatically capture as part of the authorisation.\n> This endpoint is part of our [classic API integration](https://docs.adyen.com/online-payments/classic-integrations/api-integration-ecommerce). If using a [newer integration](https://docs.adyen.com/online-payments), use the [`/payments`](https://docs.adyen.com/api-explorer/#/CheckoutService/payments) endpoint under Checkout API instead.",
"operationId" : "post-authorise",
"x-groupName" : "Payments",
"x-sortIndex" : 1,
"x-methodName" : "authorise",
"security" : [
Expand Down Expand Up @@ -168,7 +163,6 @@
"summary" : "Complete a 3DS authorisation",
"description" : "For an authenticated 3D Secure session, completes the payment authorisation. This endpoint must receive the `md` and `paResponse` parameters that you get from the card issuer after a shopper pays via 3D Secure.\n\n> This endpoint is part of our [classic API integration](https://docs.adyen.com/online-payments/classic-integrations/api-integration-ecommerce/3d-secure). If using a [newer integration](https://docs.adyen.com/online-payments), use the [`/payments/details`](https://docs.adyen.com/api-explorer/#/CheckoutService/payments/details) endpoint under Checkout API instead.",
"operationId" : "post-authorise3d",
"x-groupName" : "Payments",
"x-sortIndex" : 2,
"x-methodName" : "authorise3d",
"security" : [
Expand Down Expand Up @@ -282,7 +276,6 @@
"summary" : "Cancel an authorisation",
"description" : "Cancels the authorisation hold on a payment, returning a unique reference for this request. You can cancel payments after authorisation only for payment methods that support distinct authorisations and captures.\n\nFor more information, refer to [Cancel](https://docs.adyen.com/online-payments/classic-integrations/modify-payments/cancel).\n\n> This endpoint is part of our [classic API integration](https://docs.adyen.com/online-payments/classic-integrations/api-integration-ecommerce). If using a [newer integration](https://docs.adyen.com/online-payments), use the [`/payments/{paymentPspReference}/cancels`](https://docs.adyen.com/api-explorer/#/CheckoutService/payments/{paymentPspReference}/cancels) endpoint under Checkout API instead.",
"operationId" : "post-cancel",
"x-groupName" : "Modifications",
"x-sortIndex" : 2,
"x-methodName" : "cancel",
"security" : [
Expand Down Expand Up @@ -396,7 +389,6 @@
"summary" : "Cancel or refund a payment",
"description" : "Cancels a payment if it has not been captured yet, or refunds it if it has already been captured. This is useful when it is not certain if the payment has been captured or not (for example, when using auto-capture).\n\nDo not use this endpoint for payments that involve:\n * [Multiple partial captures](https://docs.adyen.com/online-payments/capture).\n * [Split data](https://docs.adyen.com/marketplaces-and-platforms/processing-payments#providing-split-information) either at time of payment or capture for Adyen for Platforms.\n\n Instead, check if the payment has been captured and make a corresponding [`/refund`](https://docs.adyen.com/api-explorer/#/Payment/refund) or [`/cancel`](https://docs.adyen.com/api-explorer/#/Payment/cancel) call.\n\nFor more information, refer to [Cancel or refund](https://docs.adyen.com/online-payments/classic-integrations/modify-payments/cancel-or-refund).\n\n> This endpoint is part of our [classic API integration](https://docs.adyen.com/online-payments/classic-integrations/api-integration-ecommerce). If using a [newer integration](https://docs.adyen.com/online-payments), use the [`/payments/{paymentPspReference}/reversals`](https://docs.adyen.com/api-explorer/#/CheckoutService/payments/{paymentPspReference}/reversals) endpoint under Checkout API instead.",
"operationId" : "post-cancelOrRefund",
"x-groupName" : "Modifications",
"x-sortIndex" : 4,
"x-methodName" : "cancelOrRefund",
"security" : [
Expand Down Expand Up @@ -515,7 +507,6 @@
"summary" : "Capture an authorisation",
"description" : "Captures the authorisation hold on a payment, returning a unique reference for this request. Usually the full authorisation amount is captured, however it's also possible to capture a smaller amount, which results in cancelling the remaining authorisation balance.\n\nPayment methods that are captured automatically after authorisation don't need to be captured. However, submitting a capture request on these transactions will not result in double charges. If immediate or delayed auto-capture is enabled, calling the capture method is not neccessary.\n\nFor more information refer to [Capture](https://docs.adyen.com/online-payments/classic-integrations/modify-payments/capture).\n\n> This endpoint is part of our [classic API integration](https://docs.adyen.com/online-payments/classic-integrations/api-integration-ecommerce). If using a [newer integration](https://docs.adyen.com/online-payments), use the [`/payments/{paymentPspReference}/captures`](https://docs.adyen.com/api-explorer/#/CheckoutService/v67/post/payments/{paymentPspReference}/captures) endpoint on Checkout API instead.\n\n",
"operationId" : "post-capture",
"x-groupName" : "Modifications",
"x-sortIndex" : 1,
"x-methodName" : "capture",
"security" : [
Expand Down Expand Up @@ -634,7 +625,6 @@
"summary" : "Refund a captured payment",
"description" : "Refunds a payment that has previously been captured, returning a unique reference for this request. Refunding can be done on the full captured amount or a partial amount. Multiple (partial) refunds will be accepted as long as their sum doesn't exceed the captured amount. Payments which have been authorised, but not captured, cannot be refunded, use the /cancel method instead.\n\nSome payment methods/gateways do not support partial/multiple refunds.\nA margin above the captured limit can be configured to cover shipping/handling costs.\n\nFor more information, refer to [Refund](https://docs.adyen.com/online-payments/classic-integrations/modify-payments/refund).\n\n> This endpoint is part of our [classic API integration](https://docs.adyen.com/online-payments/classic-integrations/api-integration-ecommerce). If using a [newer integration](https://docs.adyen.com/online-payments), use the [`/payments/{paymentPspReference}/refunds`](https://docs.adyen.com/api-explorer/#/CheckoutService/payments/{paymentPspReference}/refunds) endpoint under Checkout API instead.",
"operationId" : "post-refund",
"x-groupName" : "Modifications",
"x-sortIndex" : 3,
"x-methodName" : "refund",
"security" : [
Expand Down Expand Up @@ -754,7 +744,6 @@
"description" : "This endpoint allows you to cancel an unreferenced refund request before it has been completed.\n\nIn your call, you can refer to the original refund request either by using the `tenderReference`, or the `pspReference`. We recommend implementing based on the `tenderReference`, as this is generated for both offline and online transactions.\n\nFor more information, refer to [Cancel an unreferenced refund](https://docs.adyen.com/point-of-sale/refund-payment/cancel-unreferenced).",
"x-addedInVersion" : "25",
"operationId" : "post-voidPendingRefund",
"x-groupName" : "Modifications",
"x-sortIndex" : 7,
"x-methodName" : "voidPendingRefund",
"security" : [
Expand Down
Loading

0 comments on commit 35f2c0a

Please sign in to comment.