Merge pull request #206 from recurly/v3-v2021-02-25-7561215547

Generated Latest Changes for v2021-02-25

fraud_risk_rule.go

@@ -0,0 +1,122 @@
+// This file is automatically created by Recurly's OpenAPI generation process
+// and thus any edits you make by hand will be lost. If you wish to make a
+// change to this file, please create a Github issue explaining the changes you
+// need and we will usher them to the appropriate places.
+package recurly
+
+import (
+	"context"
+	"net/http"
+)
+
+type FraudRiskRule struct {
+	recurlyResponse *ResponseMetadata
+
+	// The Kount rule number.
+	Code string `json:"code,omitempty"`
+
+	// Description of why the rule was triggered
+	Message string `json:"message,omitempty"`
+}
+
+// GetResponse returns the ResponseMetadata that generated this resource
+func (resource *FraudRiskRule) GetResponse() *ResponseMetadata {
+	return resource.recurlyResponse
+}
+
+// setResponse sets the ResponseMetadata that generated this resource
+func (resource *FraudRiskRule) setResponse(res *ResponseMetadata) {
+	resource.recurlyResponse = res
+}
+
+// internal struct for deserializing accounts
+type fraudRiskRuleList struct {
+	ListMetadata
+	Data            []FraudRiskRule `json:"data"`
+	recurlyResponse *ResponseMetadata
+}
+
+// GetResponse returns the ResponseMetadata that generated this resource
+func (resource *fraudRiskRuleList) GetResponse() *ResponseMetadata {
+	return resource.recurlyResponse
+}
+
+// setResponse sets the ResponseMetadata that generated this resource
+func (resource *fraudRiskRuleList) setResponse(res *ResponseMetadata) {
+	resource.recurlyResponse = res
+}
+
+// FraudRiskRuleList allows you to paginate FraudRiskRule objects
+type FraudRiskRuleList struct {
+	client         HTTPCaller
+	requestOptions *RequestOptions
+	nextPagePath   string
+	hasMore        bool
+	data           []FraudRiskRule
+}
+
+func NewFraudRiskRuleList(client HTTPCaller, nextPagePath string, requestOptions *RequestOptions) *FraudRiskRuleList {
+	return &FraudRiskRuleList{
+		client:         client,
+		requestOptions: requestOptions,
+		nextPagePath:   nextPagePath,
+		hasMore:        true,
+	}
+}
+
+type FraudRiskRuleLister interface {
+	Fetch() error
+	FetchWithContext(ctx context.Context) error
+	Count() (*int64, error)
+	CountWithContext(ctx context.Context) (*int64, error)
+	Data() []FraudRiskRule
+	HasMore() bool
+	Next() string
+}
+
+func (list *FraudRiskRuleList) HasMore() bool {
+	return list.hasMore
+}
+
+func (list *FraudRiskRuleList) Next() string {
+	return list.nextPagePath
+}
+
+func (list *FraudRiskRuleList) Data() []FraudRiskRule {
+	return list.data
+}
+
+// Fetch fetches the next page of data into the `Data` property
+func (list *FraudRiskRuleList) FetchWithContext(ctx context.Context) error {
+	resources := &fraudRiskRuleList{}
+	err := list.client.Call(ctx, http.MethodGet, list.nextPagePath, nil, nil, list.requestOptions, resources)
+	if err != nil {
+		return err
+	}
+	// copy over properties from the response
+	list.nextPagePath = resources.Next
+	list.hasMore = resources.HasMore
+	list.data = resources.Data
+	return nil
+}
+
+// Fetch fetches the next page of data into the `Data` property
+func (list *FraudRiskRuleList) Fetch() error {
+	return list.FetchWithContext(context.Background())
+}
+
+// Count returns the count of items on the server that match this pager
+func (list *FraudRiskRuleList) CountWithContext(ctx context.Context) (*int64, error) {
+	resources := &fraudRiskRuleList{}
+	err := list.client.Call(ctx, http.MethodHead, list.nextPagePath, nil, nil, list.requestOptions, resources)
+	if err != nil {
+		return nil, err
+	}
+	resp := resources.GetResponse()
+	return resp.TotalRecords, nil
+}
+
+// Count returns the count of items on the server that match this pager
+func (list *FraudRiskRuleList) Count() (*int64, error) {
+	return list.CountWithContext(context.Background())
+}

invoice.go

@@ -55,14 +55,16 @@ type Invoice struct {
 	// Integer paired with `Net Terms Type` and representing the number
 	// of days past the current date (for `net` Net Terms Type) or days after
 	// the last day of the current month (for `eom` Net Terms Type) that the
-	// invoice will become past due. For any value, an additional 24 hours is
+	// invoice will become past due. For `manual` collection method, an additional 24 hours is
 	// added to ensure the customer has the entire last day to make payment before
-	// becoming past due.  For example:
+	// becoming past due. For example:
 	// If an invoice is due `net 0`, it is due 'On Receipt' and will become past due 24 hours after it's created.
 	// If an invoice is due `net 30`, it will become past due at 31 days exactly.
 	// If an invoice is due `eom 30`, it will become past due 31 days from the last day of the current month.
+	// For `automatic` collection method, the additional 24 hours is not added. For example, On-Receipt is due immediately, and `net 30` will become due exactly 30 days from invoice generation, at which point Recurly will attempt collection.
 	// When `eom` Net Terms Type is passed, the value for `Net Terms` is restricted to `0, 15, 30, 45, 60, or 90`.
-	// For more information please visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+	// For more information on how net terms work with `manual` collection visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+	// or visit (https://docs.recurly.com/docs/automatic-invoicing-terms#section-collection-terms) for information about net terms using `automatic` collection.
 	NetTerms int `json:"net_terms,omitempty"`
 
 	// Optionally supplied string that may be either `net` or `eom` (end-of-month).

invoice_create.go

@@ -23,14 +23,16 @@ type InvoiceCreate struct {
 	// Integer paired with `Net Terms Type` and representing the number
 	// of days past the current date (for `net` Net Terms Type) or days after
 	// the last day of the current month (for `eom` Net Terms Type) that the
-	// invoice will become past due. For any value, an additional 24 hours is
+	// invoice will become past due. For `manual` collection method, an additional 24 hours is
 	// added to ensure the customer has the entire last day to make payment before
-	// becoming past due.  For example:
+	// becoming past due. For example:
 	// If an invoice is due `net 0`, it is due 'On Receipt' and will become past due 24 hours after it's created.
 	// If an invoice is due `net 30`, it will become past due at 31 days exactly.
 	// If an invoice is due `eom 30`, it will become past due 31 days from the last day of the current month.
+	// For `automatic` collection method, the additional 24 hours is not added. For example, On-Receipt is due immediately, and `net 30` will become due exactly 30 days from invoice generation, at which point Recurly will attempt collection.
 	// When `eom` Net Terms Type is passed, the value for `Net Terms` is restricted to `0, 15, 30, 45, 60, or 90`.
-	// For more information please visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+	// For more information on how net terms work with `manual` collection visit our docs page (https://docs.recurly.com/docs/manual-payments#section-collection-terms)
+	// or visit (https://docs.recurly.com/docs/automatic-invoicing-terms#section-collection-terms) for information about net terms using `automatic` collection.
 	NetTerms *int `json:"net_terms,omitempty"`
 
 	// Optionally supplied string that may be either `net` or `eom` (end-of-month).