Subscribe (2020.09)

Content

Announcements

There are no announcements for the 2020.09 release.

MarketONE Subscribe Features

This release includes the following new general Subscribe features:

Token Support

Tokens Balances are now supported in REST, and token operations are in Parity with SOAP. You are now able to increment and decrement Token balances, accumulate a token balance when purchasing a qualified product, and use the token balance to purchase products priced in tokens. Refunds are also supported. These operations are supported in REST API calls. Portal UI changes are pending and not part of the release.

Add/Edit Campaign Type: Coupon

You can now create the campaign type: Coupon using the REST Create Campaign call.

Note: This ticket only covers REST API calls. UI support for the Portal is being handled in a separate ticket, which has a different release process.

Bug Fixes

Summary Description
Autobill:Stop Notifications giving wrong status An issue was causing AutoBill:Stop Push notifications to sometimes report the AutoBill status as Active when it's actual state was Canceled. This was fixed.
Use of AWS SFTP details in scheduled reports An issue preventing Subscribe Reports from being SFTP'd into AWS S3 buckets was resolved.
Subscribe fails to send back (retry) the processed transactions to MarketONE Subscribe batch processing was not retrying ExternalBilling transactions when error responses were provided by the ExternalBilling payment provider. This has been fixed so that:
- if the ExternalBilling transactions file cannot be processed by the Payment Provider, all transactions referenced in that specific file/batch are retried per common platform behavior
- if a single transaction is declined with a configured soft error response code, that transaction is retried per common platform behavior
Status not changed to Active after 24 hours An update was made to recurring billing processing to properly update the status of zero amount transactions, which use a PaymentMethod of type ExternalBilling, to "Captured" after the External Billing timeout is reached.
BillTransaction API giving error Failed to schedule billing attempts An issue with the Retain ExternalBilling API returning a "Failed to schedule billing attempts" when calling with an existing Payment Method ID was resolved.
REST GET Transaction calls missing subscription_item objects A bug in which the Subscribe REST API was failing to return a list of subscription_items in certain GET Subscription-by-ID scenarios was fixed.
Portal 2.0 user preferences JSON get truncated An issue preventing Portal users from logging into Portal 2.0 was fixed.
Add merchant option to control overriding/auto populating of blank fields with default address information The Subscribe platform had previously been filling in default values for any missing value in the billing address field when the payment provider is CyberSource, in order to comply with CyberSource requirements. CyberSource has added an option for the merchant config to allow empty values in the billing address field. We have now added a new merchant configuration option to prevent Subscribe from filling in blank fields if they are empty in the billing address. Note that this change must be coordinated with CyberSource to ensure that they have set the merchant configuration to allow empty values in the billing address before it can be modified in the Subscribe platform. Please contact Vindicia customer support for more information.
Account::updatePaymentMethod creates Validation transaction when using updateBehavior Update (Production + Prodtest) Beginning in Subscribe version 27.0.2, a change was introduced that caused an erroneous validation transaction to be initiated when calling account.updatePaymentMethod with the behavior set to Update. This has been corrected to not initiate a validation transaction when the behavior is set to Update.

Known Issues

This release has the following known issue:

Summary Description
Token support in REST In Vindicia Subscribe, currently only the first product is being checked to determine whether it qualifies for token accumulation. For example, when a subscription has 3 line items, only the first product (line item) is being considered for token accumulation. This is also the case in SOAP. This issue is being addressed in a separate ticket.