Product Configuration

Product-level configurations define the characteristics of different types of credit card products offered to end users. In this context, it is important to remember that, within MO’s Core, a Product is similar to a Customer Segment, as each Product requires a defined credit line range for eligibility.

In MO’s Core, issuers can create and configure as many Products as they want for their customer base, without being restricted by the BINs they have access to. For example, within the same BIN for a Gold Mastercard, the issuer can configure three different products:

Gold Class A: For users with a credit line of $5,000 and above
Gold Class B: For users with a credit line between $3,000 and $4,999
Gold Class C: For users with a credit line between $1,000 and $2,999

The configurable parameters at the Product level are:

Name – Name of the Product.

Minimum Credit Line – The minimum credit line a customer must have to qualify for the Product.

Maximum Credit Line – The upper limit of the credit line range required to access the Product.

Closing Tolerance – Configured amount to consider a confirmed transaction as paid. Example: If a customer makes a $1,000 transaction and a payment covering $999 of the principal, and this parameter is set to 1 or higher, a credit note will be automatically generated, and the transaction status will change to "Paid."

Decimal Places – The number of decimal places to consider for amounts calculated by the Core.

Decimal Round Way – Rounding method to achieve the specified decimal precision. This can be configured to round up or down.

Status – The Product’s status, which can be set as 'Active,' 'Inactive,' or 'Archived.'

Payment Days – The available payment due dates that the issuer provides to end users. Example: Users with the Gold Class A product can select a due date on the 5th, 10th, 20th, or 30th of each month.

Onboarding Configuration – Defines the types of cards supported for the Product. The available options are:

Simple: Only virtual cards or only named physical cards.
Anonymous: Only anonymous physical cards.
Complex: Virtual cards and anonymous physical cards.
Simple extended: Virtual cards and named physical cards.

MO supports both physical and virtual cards, as well as exclusive configurations for each type. This setting does not limit the ability to have multiple options enabled.

Card Default Type – Default card type (physical or virtual) assigned when a customer is created.

Overpayment Limit Amount – The additional payment amount over the total debt allowed for customers with this Product type. Example: If this parameter is set to $100 and a customer’s total debt is $1,000, the maximum payment allowed would be $1,100. Any payment exceeding this amount will be rejected by the Core.

Card Default Brand – Card brand (Mastercard, Visa, AMEX, etc.).

Days Between Closing Day and Payment Day – The number of days between the statement closing date and the payment due date.

Minimum Days to Calculate First Payment Promise – Defines the minimum number of days before the first payment promise is generated for an account. The recommended configuration is at least 14 days to prevent early charges for newly issued cards. Example: If a customer is created on the 15th and selects the 25th as their payment date, this configuration prevents their first charge from occurring within the same month, shifting it to the following month's due date.

Minimum Payment Promise Parameter – Configures the parameters for calculating the minimum payment when the Product follows a revolving credit model. The options include:

Percentage of total debt
Percentage of outstanding balance
Percentage of credit line
Fixed amount

A value can be set for any or all of these parameters. If multiple values are configured, the minimum payment will be the highest applicable value, provided it does not exceed the total debt. If the calculated minimum payment is greater than the total debt, the debt amount will be used as the minimum payment. This parameter also allows configuring whether additional costs (such as late fees or administrative charges) should be included in the minimum payment calculation.

Default Installments – Configures the default number of installments applied to a transaction when an installment plan is enabled, but no installment data is provided. If not configured, transactions without installment data will default to a single installment.

Days to Suspend Account – Configures the number of overdue days before temporarily suspending an account. Example: If set to 5 days, an account reaching 6 days past due will be suspended until payments are up to date.

Calculate Installment Amount – Defines the method for calculating installment amounts for deferred transactions. The options are:

Same: The principal amount remains constant across all installments unless a previous installment is overdue. In that case, the overdue principal is added to the current installment.
Divide: The outstanding principal is divided equally among the remaining installments.

Refinance Type – Configures the methodology for applying refinancing options to a customer’s debt. The options are:

Capitalize Total: The total outstanding balance is converted into principal and deferred over a defined term.
Capitalize Partial: In the new debt structure, all amounts retain their original classification.

Default Offer Credit Type – MO’s Core supports both revolving credit and installment-based logic within the same Product. This parameter defines the default logic applied when both options are available, particularly for transactions that do not specify an installment term.