You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Automated commit message
* Refactor trialType usage in tests to use TrialType enum
Updated the trialType assignments in ProductPricePointsBaseTest and SubscriptionsControllerActivateTest to utilize the TrialType enum instead of string literals for improved type safety and consistency.
* Update tests to enhance property assertions and improve comparison logic
- Adjusted the expected size of additional properties in InvoicesControllerListInvoiceEventsTest.
- Updated assertions in InvoicesControllerReadCreditNoteTest to include additionalProperties in comparison.
- Refactored trialType assertions in multiple ProductPricePointsController tests to use asString() for better clarity.
- Enhanced comparison logic in SubscriptionStatusController tests to include creditCard.additionalProperties.
- Modified TestFixtures to initialize INVOICE_SELLER with null values for name, address, and phone for better test isolation.
* Enhance invoice tests by updating property assertions and initializing INVOICE_SELLER with valid data
- Modified InvoicesControllerCreateTest to include additionalProperties in the invoice discount comparison.
- Updated TestFixtures to initialize INVOICE_SELLER with specific values for name, address, and phone for improved test accuracy.
* Refactor invoice seller assertions in tests for improved clarity
- Updated assertions in InvoicesControllerCreateTest and InvoicesControllerRecordPaymentForInvoiceTest to check for null values in invoice seller properties.
- Removed the use of INVOICE_SELLER constant for a more explicit assertion approach, enhancing test readability and accuracy.
**_Note:_** Documentation for the client can be found [here.](https://www.github.com/maxio-com/ab-java-sdk/tree/7.0.1/doc/client.md)
44
+
**_Note:_** Documentation for the client can be found [here.](https://www.github.com/maxio-com/ab-java-sdk/tree/8.0.0/doc/client.md)
45
45
46
46
The following parameters are configurable for the API Client:
47
47
48
48
| Parameter | Type | Description |
49
49
| --- | --- | --- |
50
50
| site |`String`| The subdomain for your Advanced Billing site.<br>*Default*: `"subdomain"`|
51
51
| environment |`Environment`| The API environment. <br> **Default: `Environment.US`**|
52
-
| httpClientConfig |[`Consumer<HttpClientConfiguration.Builder>`](https://www.github.com/maxio-com/ab-java-sdk/tree/7.0.1/doc/http-client-configuration-builder.md)| Set up Http Client Configuration instance. |
53
-
| basicAuthCredentials |[`BasicAuthCredentials`](https://www.github.com/maxio-com/ab-java-sdk/tree/7.0.1/doc/auth/basic-authentication.md)| The Credentials Setter for Basic Authentication |
52
+
| httpClientConfig |[`Consumer<HttpClientConfiguration.Builder>`](https://www.github.com/maxio-com/ab-java-sdk/tree/8.0.0/doc/http-client-configuration-builder.md)| Set up Http Client Configuration instance. |
53
+
| basicAuthCredentials |[`BasicAuthCredentials`](https://www.github.com/maxio-com/ab-java-sdk/tree/8.0.0/doc/auth/basic-authentication.md)| The Credentials Setter for Basic Authentication |
54
54
55
55
The API client can be initialized as follows:
56
56
@@ -94,67 +94,67 @@ The SDK can be configured to use a different environment for making API calls. A
94
94
95
95
This API uses the following authentication schemes.
Generate an invoice in advance for a subscription's next renewal date. [Please see our docs](https://maxio.zendesk.com/hc/en-us/articles/24252026404749-Issue-Invoice-In-Advance) for more information on advance invoices, including eligibility on generating one; for the most part, they function like any other invoice, except they are issued early and have special behavior upon being voided.
20
+
Generate an invoice in advance for a subscription's next renewal date. [See our docs](https://maxio.zendesk.com/hc/en-us/articles/24252026404749-Issue-Invoice-In-Advance) for more information on advance invoices, including eligibility on generating one; for the most part, they function like any other invoice, except they are issued early and have special behavior upon being voided.
21
21
A subscription may only have one advance invoice per billing period. Attempting to issue an advance invoice when one already exists will return an error.
22
22
That said, regeneration of the invoice may be forced with the params `force: true`, which will void an advance invoice if one exists and generate a new one. If no advance invoice exists, a new one will be generated.
23
23
We recommend using either the create or preview endpoints for proforma invoices to preview this advance invoice before using this endpoint to generate it.
@@ -109,7 +109,7 @@ try {
109
109
# Void Advance Invoice
110
110
111
111
Void a subscription's existing advance invoice. Once voided, it can later be regenerated if desired.
112
-
A `reason` is required in order to void, and the invoice must have an open status. Voiding will cause any prepayments and credits that were applied to the invoice to be returned to the subscription. For a full overview of the impact of voiding, please [see our help docs](../../doc/models/invoice.md).
112
+
A `reason` is required in order to void, and the invoice must have an open status. Voiding will cause any prepayments and credits that were applied to the invoice to be returned to the subscription. For a full overview of the impact of voiding, [see our help docs](../../doc/models/invoice.md).
Copy file name to clipboardExpand all lines: doc/controllers/billing-portal.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ If your customer has been invited to the Billing Portal, then they will receive
32
32
33
33
If you need to provide your customer their Management URL through other means, you can retrieve it via the API. Because the URL is cryptographically signed with a timestamp, it is not possible for merchants to generate the URL without requesting it from Advanced Billing.
34
34
35
-
In order to prevent abuse & overuse, we ask that you request a new URL only when absolutely necessary. Management URLs are good for 65 days, so you should re-use a previously generated one as much as possible. If you use the URL frequently (such as to display on your website), please **do not** make an API request to Advanced Billing every time.
35
+
In order to prevent abuse & overuse, we ask that you request a new URL only when absolutely necessary. Management URLs are good for 65 days, so you should re-use a previously generated one as much as possible. If you use the URL frequently (such as to display on your website), **do not** make an API request to Advanced Billing every time.
0 commit comments