POST/invoices request, you can create an Invoice in either a draft or open state. If you don't provide a value, the default is open.POST/invoices request in an open state.draft state means you're not yet authorizing Digital River to capture the charge. Because invoices created in this state contain the total taxes, fees, duties, and amounts for the goods rendered, they can be useful for emailing renewal reminders to customers.customerIdsourceIdcurrencystatelocaleshipTodiscountcollectionPeriodDaysbillingOptimizationitemstaxInclusivetaxIdentifierschargeTypecustomerTypeupstreamIdPOST/invoices/{id}/open request to open an invoice. Only invoices in a draft state can be opened. By submitting this request, you are instructing Digital River to initiate the invoice billing process.POST/invoices/{id}/void request to void an invoice. Voiding is similar to deleting an invoice but maintains a record of when the invoice was created, opened, and voided.void state are not payable. If you receive payment from the customer outside of the normal flow (e.g., the customer pays by check) you should void the invoice. This is also a terminal state, which means voided invoices can never transition to another state.open state can be voided. If you attempt to void an invoice in any other state, you'll receive a 409 Conflict response.DELETE/invoices/{id} request to permanently delete an invoice. This action is similar to voiding an invoice but no record is maintained for accounting purposes. You can only delete an invoice when it is in a draft state.open state or submit an open invoice request, Digital River starts the billing process and attempts to capture the charge.billingOptimization to true. This instructs Digital River to make multiple payment capture attempts over a period of time whose length you can specify using the collectionPeriodDays parameter. The default setting is 30 days. collectionPeriodDays, if one of the internal orders that Digital River generates is able to successfully capture the charge, we move the Invoice into a paid state. However, if we're unable to collect payment within this time period, we mark the Invoice as uncollectibleand emit an invoice.uncollectible event.attemptCount attribute. This value can be useful for your analytics.billingOptimization to false means we attempt to collect payment just one-time. In this case, collectionPeriodDays has no effect on the billing process. After that one collection attempt, depending on the result, we move the Invoice into either a paid or uncollectible state and then emit the appropriate events.billingOptimization to true, we recommend you only allow customers to make purchases with credit cards. draft, open, paid, uncollectible, or void.open state, it can either become void, paid, or uncollectible. All of these are terminal states, meaning they can never transition to another state. Invoices that move into a void or uncollectible state are not payable.state values for a successful Invoice (i.e. the happy path) are draft > open > paid .state changes from open to paid both an invoice.paid and an invoice.updated event are emitted.draftinvoice.createdopeninvoice.created and an invoice.openopeninvoice.open and an invoice.updatedpaidinvoice.paid and an invoice.updatedvoidinvoice.void and an invoice.updateduncollectibleinvoice.uncollectible and an invoice.updated