Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(charges): Add Charge.regroup_paid_fees attribute #251

Merged
merged 1 commit into from
Jul 17, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 45 additions & 0 deletions openapi.yaml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

13 changes: 13 additions & 0 deletions src/schemas/ChargeObject.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,19 @@ properties:
type: boolean
description: This field specifies whether the charge should be included in a proper invoice. If set to `false`, no invoice will be issued for this charge. You can only set it to `false` when `pay_in_advance` is `true`.
example: true
regroup_paid_fees:
type: string
nullable: true
enum:
- null
- invoice
description: |-
This setting can only be configured if `pay_in_advance` is `true` and `invoiceable` is `false`.
This field determines whether and when the charge fee should be included in
the invoice. If `null`, no invoice will be issued for this charge fee.
If `invoice`, an invoice will be generated at the end of the period,
consolidating all charge fees with a succeeded payment status.
example: "invoice"
prorated:
type: boolean
example: false
Expand Down
15 changes: 15 additions & 0 deletions src/schemas/PlanCreateInput.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,19 @@ properties:
type: boolean
description: This field specifies whether the charge should be included in a proper invoice. If set to false, no invoice will be issued for this charge. You can only set it to `false` when `pay_in_advance` is `true`.
example: true
regroup_paid_fees:
type: string
nullable: true
enum:
- null
- invoice
description: |-
This setting can only be configured if `pay_in_advance` is `true` and `invoiceable` is `false`.
This field determines whether and when the charge fee should be included in
the invoice. If `null`, no invoice will be issued for this charge fee.
If `invoice`, an invoice will be generated at the end of the period,
consolidating all charge fees with a succeeded payment status.
example: "invoice"
invoice_display_name:
type: string
description: Specifies the name that will be displayed on an invoice. If no value is set for this field, the name of the actual charge will be used as the default display name.
Expand Down Expand Up @@ -146,6 +159,7 @@ properties:
invoiceable: true
invoice_display_name: "Setup"
pay_in_advance: false
regroup_paid_fees: null
prorated: false
min_amount_cents: 3000
properties:
Expand Down Expand Up @@ -216,6 +230,7 @@ properties:
invoiceable: false
invoice_display_name: "Setup"
pay_in_advance: true
regroup_paid_fees: "invoice"
prorated: false
min_amount_cents: 0
properties:
Expand Down
2 changes: 2 additions & 0 deletions src/schemas/PlanObject.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -91,6 +91,7 @@ properties:
invoiceable: true
invoice_display_name: "Setup"
pay_in_advance: false
regroup_paid_fees: null
prorated: false
min_amount_cents: 3000
properties:
Expand Down Expand Up @@ -175,6 +176,7 @@ properties:
invoiceable: false
invoice_display_name: "Setup"
pay_in_advance: true
regroup_paid_fees: "invoice"
prorated: false
min_amount_cents: 0
properties:
Expand Down
15 changes: 15 additions & 0 deletions src/schemas/PlanUpdateInput.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,19 @@ properties:
type: boolean
description: This field specifies whether the charge should be included in a proper invoice. If set to false, no invoice will be issued for this charge. You can only set it to `false` when `pay_in_advance` is `true`.
example: true
regroup_paid_fees:
type: string
nullable: true
enum:
- null
- invoice
description: |-
This setting can only be configured if `pay_in_advance` is `true` and `invoiceable` is `false`.
This field determines whether and when the charge fee should be included in
the invoice. If `null`, no invoice will be issued for this charge fee.
If `invoice`, an invoice will be generated at the end of the period,
consolidating all charge fees with a succeeded payment status.
example: "invoice"
invoice_display_name:
type: string
description: Specifies the name that will be displayed on an invoice. If no value is set for this field, the name of the actual charge will be used as the default display name.
Expand Down Expand Up @@ -182,6 +195,7 @@ properties:
invoiceable: true
invoice_display_name: "Setup"
pay_in_advance: true
regroup_paid_fees: null
prorated: false
min_amount_cents: 0
properties: {}
Expand Down Expand Up @@ -221,6 +235,7 @@ properties:
invoiceable: false
invoice_display_name: "Setup"
pay_in_advance: true
regroup_paid_fees: "invoice"
prorated: false
min_amount_cents: 0
properties:
Expand Down
Loading