V2
This topic shows information relevant specifically for Subscribe REST API version 20210401 referred to as V2 Subscribe Transactions typically represent requests for funds sent to a payment processor. The Transaction object provides a way to charge a customer. You can create one-time transactions, retrieve individual transactions, fetch individual transactions, and list all Transactions for a given account or subscription. The Transaction request includes a Payment Method, customer Account information (including Billing Address), one or more Products or billing plans, a price amount and currency, as well as additional metadata used by the system. Transactions can also accept campaign codes to provide a discount to the transaction. Transactions can also accept discount tickets to provide multiple discounts to the transaction and its Items. Note: In current release, Transactions as part of a subscription support the stackable discount feature. One-time Transactions do not support it. Posting with a new Transaction creates a new one-time Transaction object. If “to_be_captured” is false, the request will trigger an authorization attempt (based on the provided payment method’s authorization process). If successfully authorized, a subsequent post to the transaction’s actions/capture endpoint will capture the authorized transaction. If you post a new transaction with “to_be_captured” true, it will authorize and immediately capture the transaction if successful. To refund transactions, use therefunds endpoint. Learn more about Transactions, in the Subscribe Portal User Guide. For more information, see Transactions in the Subscribe OpenAPIs located in the Developer Hub section of the Knowledge Center.- Transactions Supported Operations
- The Transaction Object
- Create a Transaction (Authorization)
- Capture a Transaction
- Finish a Transaction
- Cancel a Transaction
- Fetch a Specific Transaction
- List All Transactions