Implemented an onboarding application that allows for the supply of information from a merchant to the provisioning company directly. You can now provide an external software company that needs to board merchants with a brandable onboarding application that is aimed at collecting information from a merchant. The application collects all necessary information that will be further submitted to the processor that performs provisioning. Provisioning response can be delivered in real-time or via callback, which is subject to a specific processor. Please refer to Provisioning API specification for more details.
Added mechanism allowing for the assignment of priority to default settings of different system levels. You can now control what level – system, portfolio, reseller – is prioritized for defaults. Defaults assigned by a higher level can be overridden by a lower level. For example, if a portfolio has batch review enabled, a reseller can disable this setting for newly created associated merchants by configuring a setting on the Defaults form. If no defaults on a level lower than system is enabled, system settings set as defaults are applicable. To override a setting, configure it as needed and then click the enable button via the Defaults form on the Reseller and Portfolio perspectives.
Added extended validation mechanism to the provisioning API, the user interface and information obtained from a processor. The validation mechanism for onboarding application works similiar to the same mechanism within the gateway. Validation works both for visible and hidden fields and pages now.
Moved support system settings from System to Portfolio perspective. You can now set up support system credentials for a particular portfolio using the Details form on the Portfolio perspective. Previously, the ability to control support system settings was available for the entire system only.
Processor Type Field
Added ability to control whether transaction search by a processor is available within the system. You can now hide the Processor Type field for Portfolio1 and Portfolio2 security levels. For users that are lower than portfolio this field is now always unavailable. Previously, search by processor code was available for all security levels, so merchants could see the information about all processors within the system. Please refer to Security Management Guide under Self-study section for additional information about security levels.
IDs in Provisioning API
Renamed code related fields in Provisioning API. resellerCode, merchantCode, merchantAccountCode and portfolioCode fields were renamed to resellerId, merchantId, accountId and portfolioId respectively. Previously, fields with code in the name could cause confusion because of their respective names on the user interface. If reseller reference code is submitted within resellerId field, the value must be preceded by an asterisk (i.e. resellerId=*00001).
Driver License Country Code
Added driver licence country code to the business information about merchant. You can now provide information about a merchant’s driver license country on the Business Owner form on the Merchant perspective. Previously, only driver license state information could be added.
Gift Card Management
Added ability to control whether API operations with gift cards are available for a particular processor or not. You can now manage whether gift cards operations are available while processing with particular providers. By default, Heartland, STS, FD Rapid Connect and Vantiv processors can accept API calls associated with gift cards. Previously, there was no ability to switch off gift card processing within the system. Gift card processing with a particular provider can be controlled via isCardManagementSupported field within a respective processor profile.
Real-time and Batch Fees
Added separation of fees charged to chargebacks, reversals and returns for real-time and batch transactions. You can now define whether chargebacks, reversals and returns are associated with real-time transactions or batch files. Previously there was no ability to separate real-time and batch transactions on merchant statements.
Page Management in Provisioning API
Adjusted page management mechanism in provisioning API. You can now submit one or more values without dashes and in random order within pageFormat field. Additionally, you can now submit H letter for cases when a sub-header is required to be present on the pages within the onboarding application. Previously, all values were required to be submitted in a certain order, and if one or more values should not be passed, they had to be replaced with a dash sign. Please refer to Page Management integration note under Provisioning API specification for more details.
Date of Birth Validation
Enhanced validation mechanism on the user interface of onboarding application. Only 18 years old business owners can apply for merchant accounts now. A respective validation mechanism was added to Date of Birth field. Additionally, added ability to receive information about field format being incorrect right after entering an incorrect value. Previously, an incorrect birthdate could be submitted and validation worked only after the entire form was submitted, so it could lead to cases when a user was supposed to enter all information once again.
Enhanced validation for estimates related fields within the onboarding application. You can now submit only digits within estimates fields. If no values should be submitted, these fields can be left empty. Previously, when no values should be submitted, the system still required them to be submitted.
Fixed the issue with no data sent to the URL associated with callback. Due to a bug, a user could not see provisioning response when being redirected to the one of the callback URLs (notifyURL, returnURL, cancelURL). The issue is fixed now, and when a callback is used, the respective data is shown.