| PORT-2058 | Subscribe Portal 2.0 - Text input is not submitted when pressing ENTER key | In Portal 2.0, when entering a text field when searching, pressing the ENTER key did not submit the query. The issue has been resolved. |
| PORT-2062 | Subscribe Portal 2.0 - modifying existing subscription items issue | The system did not allow to modify subscriptions that have subscription items without an id. This has been resolvedNote: When adding a new Subscription item, an ID is required. |
| PORT-2069 | Subscribe Portal 2.0 - Navigation issue from subscription page to view all related transactions. | See All transactions link from a subscription detail view was referencing an empty list. The issue has been fixed and clicking on the link displays full transaction list |
| PORT-2086 | Subscribe Portal 2.0 - The Campaign’s Currency field is limited to up to 999 | In portal 2.0, the Currency field was limited to 3 digits. This issue has been fixed. |
| PORT-2111 | Subscribe Portal 2.0 - Rate plan List Search Page navigation issue | Navigation from a rate plan list page with only one row occurred. When clicking back, resulted in an empty list. This has been fixed. |
| PORT-2113, VIN-15894 | Subscribe Portal 2.0 - Schedule reports through Reports 2.0 data engine does not display the timezone selection | In Portal 2.0, Schedule reports through Reports 2.0 did not display the timezone selection field. This has been fixed. |
| VIN-8684 | SOAP API- Changing billing day of month for a subscription that is in retry was returning success, although the activity was not performed | The SOAP API Autobill.ChangeBillingDayOfMonth method returned a success (200) response but did not change the day. This was modified and if the date cannot be changed because the subscription is in retry, the API returns a Bad request (400) response. |
| VIN-12225 | REST API - Create subscription that includes wrong metadata structure, returned success response 200 but the subscription was not created. | A POST Subscribe call that includes incorrect body structure for metadata, returned a success (200) status code but did not create the subscription This has been fixed. |
| VIN-14863 | Orbital Integration -New or renewal transactions processed through Orbital with tokenized credit card payment methods, rejected | Unable to create or renew subscriptions with tokens for Orbital. This has been resolved. |
| VIN-14864 | Retain - Stripe Chargeback Feed is not reaching the correct endpoint | Merchants that use Stripe as a payment provider and use Vindicia Retain, will now get the chargeback feed automatically. |
| VIN-15399 | Orbital Integration - Refunds for subscriptions that have tokenized payment methods and orbital as processor are not successful | Refunds for subscriptions that have tokenized payment methods and use Orbital as the payment provider were not passed successfully. This has been fixed. |
| VIN-15451 | WorldPay Integration - Subscriptions processed through WorldPay require different handling of the MIT token, based on their creation date. | The method for handling recurring transactions for WorldPay has been updated to take into account subscriptions that are more than two years old. |
| VIN-15558 | Portal 2.0- Chargeback Changes Report was missing columns. | The Chargeback Changes Report issued though Portal 2.0 was missing Affiliate ID and SubAffiliate ID columns. This has been resolved. |
| VIN-15819 | Adyen Integration- Issue with passing amounts for currencies that do not support decimals | There are several currencies that do not support decimals. In those cases, Subscribe was passing the amount to the processor with additional digits.Adyen processes these type of currencies differently. The issue was fixed according to the Adyen approach. |
