Skip to content

Commit

Permalink
rerun konfig fix
Browse files Browse the repository at this point in the history
  • Loading branch information
@dphuang2
dphuang2 committed Sep 12, 2023
1 parent 8739f11 commit 9fdcf07
Showing 1 changed file with 10 additions and 30 deletions.
40 changes: 10 additions & 30 deletions swagger-fixed.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,8 @@
"/api/installmentplans/{installmentPlanNumber}": {
"get": {
"tags": [
"Fetch Plans"
"InstallmentPlan"
],
"summary": "Fetch Plan by Number",
"operationId": "InstallmentPlan_Get",
"security": [
{
Expand All @@ -26,7 +25,6 @@
]
}
],
"description": "Retrieve an installment plan's information by providing its number in your path.",
"parameters": [
{
"name": "installmentPlanNumber",
Expand Down Expand Up @@ -168,9 +166,8 @@
"/api/installmentplans/search": {
"get": {
"tags": [
"Fetch Plans"
"InstallmentPlan"
],
"summary": "Fetch Plan(s) by Alternate Field",
"operationId": "InstallmentPlan_Search",
"security": [
{
Expand All @@ -179,7 +176,6 @@
]
}
],
"description": "Retrieves a plan by RefOrderNumber or ExtendedParams. Note that RefOrderNumber or ExtendedParams were optionally specified by you upon plan creation.",
"parameters": [
{
"name": "installmentPlanNumber",
Expand Down Expand Up @@ -339,9 +335,8 @@
"/api/installmentplans/initiate": {
"post": {
"tags": [
"Start Plans (Splitit Forms)"
"InstallmentPlan"
],
"summary": "Initiate Installment Plan",
"operationId": "InstallmentPlan_Post",
"security": [
{
Expand All @@ -350,7 +345,6 @@
]
}
],
"description": "Initiate establishes an installment plan but doesn't finalize it, and is thus intended for use with Splitit premade checkout solutions such as Payment Forms or Flex Form. Initiate only requires SAQ-A certification. You can call it multiple times for the same installment plan, since each time a new API call is made, existing data will be updated and new values will be appended to the existing plan. Note that for funded plans, a customer's BillingAddress object must be filled out.",
"parameters": [
{
"name": "X-Splitit-TestMode",
Expand Down Expand Up @@ -548,9 +542,8 @@
"/api/installmentplans": {
"post": {
"tags": [
"Start Plans (Direct API)"
"InstallmentPlan"
],
"summary": "Create Installment Plan",
"operationId": "InstallmentPlan_Post2",
"security": [
{
Expand All @@ -559,7 +552,6 @@
]
}
],
"description": "Once you are ready to check your customer out, you can use the Create endpoint. Create enables you to pass in PCI sensitive data directly to the Splitit API, and thus requires SAQ-D PCI certification.\nA successful Create operation creates an authorization on a customer's credit card, and if AutoCapture has been set to true within the request body, both authorization and capture of the first installment will be completed (if AutoCapture is set to false, you will have to call Update Plan later). If Splitit is unable to successfully secure an authorization on a credit card, an error message will be returned in the response. Note that for funded plans, a customer's BillingAddress object must be filled out. In addition, if you are completely managing the input of PCI sensitive data on your side, it’s essential to ensure your customer has approved the Splitit specific terms and conditions.\n",
"parameters": [
{
"name": "X-Splitit-TestMode",
Expand Down Expand Up @@ -757,9 +749,8 @@
"/api/installmentplans/{installmentPlanNumber}/verifyauthorization": {
"get": {
"tags": [
"Start Plans (Splitit Forms)"
"InstallmentPlan"
],
"summary": "Verify Authorization",
"operationId": "InstallmentPlan_VerifyAuthorization",
"security": [
{
Expand All @@ -768,7 +759,6 @@
]
}
],
"description": "You must call Verify Authorization in cases when plan authorization and order closure do not happen simultaneously. An example of this would be when a customer checks out with a Payment Form or Flex Form, or is redirected for 3DS. To call it, you need to provide the plan number you received in the success response from Initiate.",
"parameters": [
{
"name": "installmentPlanNumber",
Expand Down Expand Up @@ -910,9 +900,8 @@
"/api/installmentplans/{installmentPlanNumber}/updateorder": {
"put": {
"tags": [
"Maintain Plans"
"InstallmentPlan"
],
"summary": "Update Plan by Number",
"operationId": "InstallmentPlan_UpdateOrder",
"security": [
{
Expand All @@ -921,7 +910,6 @@
]
}
],
"description": "Locate a plan by installment number then carry out post-authorization activities related to the plan, such as updating the order number, updating the tracking number, or updating shipping status. You can also use this endpoint to capture the first installment from a plan that has only been authorized but not yet captured.",
"parameters": [
{
"name": "installmentPlanNumber",
Expand Down Expand Up @@ -1089,9 +1077,8 @@
"/api/installmentplans/updateorder": {
"put": {
"tags": [
"Maintain Plans"
"InstallmentPlan"
],
"summary": "Update Plan By Alternate Field",
"operationId": "InstallmentPlan_UpdateOrder2",
"security": [
{
Expand All @@ -1100,7 +1087,6 @@
]
}
],
"description": "Locate a plan by RefOrderNumber or ExtendedParams then carry out post-authorization activities related to the plan, such as updating the order number, updating the tracking number, or updating shipping status. You can also use this endpoint to capture the first installment from a plan that has only been authorized but not yet captured. Note that RefOrderNumber or ExtendedParams were optionally specified by you upon plan creation.",
"parameters": [
{
"name": "X-Splitit-IdempotencyKey",
Expand Down Expand Up @@ -1259,9 +1245,8 @@
"/api/installmentplans/{installmentPlanNumber}/refund": {
"post": {
"tags": [
"Maintain Plans"
"InstallmentPlan"
],
"summary": "Refund a Plan",
"operationId": "InstallmentPlan_Refund",
"security": [
{
Expand All @@ -1270,7 +1255,6 @@
]
}
],
"description": "Refund part or all of an installment Plan.\n\nStrategies\nThere are several refund strategies you can choose when refunding a plan (note that the default is FutureInstallmentsFirst):\n\n- FutureInstallmentsFirst: At first customer isn’t refunded any installment money that they have already paid. Instead their refund lessens the amount of future installments they will be debited for, beginning with the next installment that is due. However, if their refund exceeds the amount of money they have left to pay (all installments), only then is the refund taken out of the installment money they have already paid\n- FutureInstallmentsLast: Customer is refunded beginning with the installment money they have already paid. If their refund amount exceeds the amount they have already paid, their amount of future installments due gets decreased, beginning with the next installment due and then proceeding to the later ones\n- FutureInstallmentsNotAllowed: Customer is only refunded from installment money that they have already paid, not from any future installments that they have due\n- ReduceFromLastInstallment: This is the same as FutureInstallmentsFirst, except that the refund is credited starting with the last installment first (e.g., number 6 of 6, as opposed to number 2 of 6).\n",
"parameters": [
{
"name": "installmentPlanNumber",
Expand Down Expand Up @@ -1438,9 +1422,8 @@
"/api/installmentplans/{installmentPlanNumber}/cancel": {
"post": {
"tags": [
"Maintain Plans"
"InstallmentPlan"
],
"summary": "Cancel a Plan",
"operationId": "InstallmentPlan_Cancel",
"security": [
{
Expand All @@ -1449,7 +1432,6 @@
]
}
],
"description": "The Cancel operation allows you to cancel an existing installment plan.",
"parameters": [
{
"name": "installmentPlanNumber",
Expand Down Expand Up @@ -1591,9 +1573,8 @@
"/api/installmentplans/check-eligibility": {
"post": {
"tags": [
"Start Plans (Direct API)"
"InstallmentPlan"
],
"summary": "Check Eligibility",
"operationId": "InstallmentPlan_CheckEligibility",
"security": [
{
Expand All @@ -1602,7 +1583,6 @@
]
}
],
"description": "As your customer beings to checkout, use this endpoint to verify their overall eligibility for Splitit installment plans and to determine plans for which they are eligible. This endpoint can be called repeatedly before and during checkout, for example you may call it after each field on a page is filled out. The Splitit API compares and updates the plan based on each new body as it arrives.",
"parameters": [
{
"name": "X-Splitit-IdempotencyKey",
Expand Down

0 comments on commit 9fdcf07

Please sign in to comment.