Subscription Product / Payment Support (OCC-59)

Subscription products / payments allow a product to be sold over time and should have ability to continue indefinitely, have a defined end date, or allow for canceling.

The subscription framework should be agnostic to the selected payment gateway while also recognizing only some payment gateways allow tokenization. There may be an interface that payment providers would implement to validate they support a tokenization payment model.

General architecture would be Subscription Plans and Subscription Products.

Subscription Plans

• Interval: Picklist of Day, Week, Month, Year
• Frequency: integer
• Maximum Occurrences: integer (leave blank for unlimited)
• Number of Days for Trial Period: integer (use 0 for no trial period)
• Notification Interval: Picklist of None, Day, Week, Month, Year (notifications fire off workflow event in advance of charging)
• Notification Period: integer (how many "Notification Interval" do you want to have in advance of the charge event to fire off workflow)
• Grace Interval: Picklist of None, Day, Week, Month, Year (assuming a payment is unfulfilled, what is the period before the subscription is automatically canceled)
• Grace Period: integer (how many "Grace Interval" do you want to have in advance of the failed payment before cancelling subscription)

Subscription Product

• Really this is just a "SubcriptionPart" that allows you to select a Subscription Plan (defined above)

By default, the Subscription simply continues on with the pricing as it was fixed in time at the Order, it does not recalculate pricing along the way.

Jira issue

No files, tests, or entry points are named. Start by reviewing the existing commerce and payment abstractions, then use the Jira issue OCC-59 for any additional context. Done means subscription plans and products support the listed intervals, trials, notifications, grace periods, cancellation, indefinite continuation, fixed-at-order pricing, and payment-gateway tokenization differences.