Release 64

Evertec Added for Smart Payments (Phase 1 Basic)(DEV-11471)

With this release, Aria adds the Evertec payment gateway as part of Smart Payments. Evertec, Inc. is a leading electronic transactions and technology company headquartered in San Juan, Puerto Rico. Evertec operates in 26 countries in Latin America and the Caribbean, providing services in three key areas: merchant acquiring, payment processing, and business solutions.

Navigate as follows to add Evertec as part of your integration: Configuration > Payments > Payment Gateways/Collection Groups.

The following tabs are included for Evertec configuration: 

• Merchant Account Details 
• Processing Options 
• Accepted Payment Method 

The Merchant Account Details tab contains the following fields:

The Processing Options tab contains the following section: 3DS Authentication Settings

This section contains the following field:

Evertec allows the following Accepted Payment Methods:

• Credit Card
• Tokenized Credit Card

An API-related enhancement for Evertec also appears on this page.

ACCP Create Refunds Process Updates (DEV-11597)

A new streamlined Refund processing workflow has been introduced in CCP including an intuitive interface that enhances your control and visibility of Refunds. This new workflow provides both a high-level overview and detailed control of the refund process, resulting in more efficient and accurate refund management. The following new Refund features are now available:

• A New Refund button is activated only when refundable payments are available.
• A detailed payment selection table displays the Payment ID/Transaction No. You can initiate a refund by clicking on the selected payment in the column.
• A new form validation guides you through the required fields before enabling Refund submission.

ACCP All Service Rates List View—Part 1 (DEV-11598)

The All Service Rates workflow has been redesigned to be more intuitive and adaptable for larger data sets by implementing the following new features:

• A new layout displaying a Subscription hierarchy tree, selected Subscription Details, and a Service Rates table with detailed rate information.
• An extended Rate Tier view with Rate Tier modification options.
• Custom Rates features like Rate Schedule management, Current Plan Custom Rates, and Queued Plan Custom Rates.
• Comprehensive Proration management.

ACCP Grid Filtering Implementation — Part 2 (DEV-11813)

The filtering capabilities within data tables in CCP has been expanded to allow users to quickly filter and locate information within the available data. Enhanced filtering functionality has been implemented across the following data tables in CCP:

• Account > Overview > Recent Activities > Recent Communications Grid
• Transactions > Credits > Cash Credits Grid
• Transactions > Credits (Credits tab view) > Service Credits Grid
• Transactions > Invoices Grid
• Transactions > Pending Invoices Grid
• Transactions > Payments Grid
• Subscriptions > Details Grid
• Subscriptions > Billing Group (List View tab) Grid

Tokenized Credit Cards Supported For Buckaroo Smart Payments (DEV-11858)

For Buckaroo Smart Payments, Aria now supports automatic Tokenized Credit Cards (pay method 13) for Visa, Mastercard, and American Express. The token is generated once after completing an initial payment. 

The following actions are supported for Tokenized Credit Cards: 

• Payment 
• Authorization 
• Authorize_3DS 
• Capture 
• Reversal 
• Refund (full and partial) 
• Query_Token 

ACCP Fixes and Improvements (DEV-11871)

The following fixes and enhancements have been added to CCP:

• Navigation between the legacy Aria Billing UI and CCP has been improved with account context preservation. You are now redirected to the same account being viewed when switching between the UIs. This improvement includes navigation to recently accessed page views within the same account.
• Improved performance for loading quick search criteria into the dropdown and quick search bar significantly reducing loading time for search options.
• Functionality has been added to the Subscription Details drawer, allowing you to save Usage Pooling details through a popout form. This enhancement respects the "Allow MPI Level Usage Pooling" settings. When enabled, you can modify usage pooling details; when disabled, the information is displayed in read-only mode.
• The error messaging in the Billing Group modification drawer has been enhanced when you attempt to add subscriptions that cannot be assigned. When selecting subscriptions that are not self-pay, CCP now displays the message: "One or more selected Subscriptions cannot be assigned to a Billing group at this level because their payment responsibility is already assigned to a Subscription within the Parent account."
• The Subscription Period filter now displays invoice records only within the specified date range.
• The Invoice Details drawer has been updated to display unit values for discount line items with consistent currency symbols in prorated invoices.
• The Transactions > Payments screen now shows only the relevant transactions needed for payment processing.
• The Created By value now correctly displays on the Child Accounts table within the Account Number column ensuring that information is consistently displayed when hovering over each Account No cell.
• Your selected subscription filter on the Coupon page will now remain persistent when navigating between pages until you explicitly change it.
• The Refund list has been updated to fix an issue where voided refunds were incorrectly included in the grand total calculation. This correction ensures that the displayed grand total accurately reflects only valid refunds.
• Previously missing effective dates on the Service table now display correctly.

ACCP Subscription Queued Changes List View—Part 2 (DEV-11879)

The Queued Subscription Changes interface has the following new actions available from the row actions menu giving you greater control over queued subscription modifications as well as improving the visibility of change details before execution:

• Execute Changes opens a drawer displaying Service Rates, Subscription fields, and Product fields related to the subscription allowing you to review details before confirming queued changes.
• Change Effective Date provides subscription details and allows you to modify the date that the change will go into effect.
• Delete Queued Change prompts a warning notification explaining the implications of deletion by displaying the message, "Deleting this queued subscription change will automatically delete all queued subscription changes for all associated subscription add-ons."

NSO Installments Phase 8: New Statement Loop and Strings, Enhanced Payment Application and Unapplication, and Additional UI Elements (DEV-11912)

This phase of NSO Installments introduces enhanced installment support across three Aria Billing application areas: 

1. It makes available a new statement loop with strings that provide a summarized view of statement taxes by tax type, including taxes on aligned installments, with details like tax type description, latest tax rate, base amount, and applied tax amount. 
2. It enhances core payment application and unapplication logic to support installment surcharges for both single and bulk payment transactions. 
3. It adds UI elements to create installment surcharges.

Aria has introduced a new replacement string loop beginLoopStmtAlignedInstlTaxSummary that provides information about a statement’s taxes summarized by tax type, including any taxes on aligned installments. The new available strings are:

• insertInstlTaxSummaryTypeDesc—Description of the tax type including tax for installment and installment surcharge
• insertInstlTaxSummaryRate—The most recent rate assigned to the tax type. Older aligned installments may have been taxed at a different rate.
• insertInstlTaxSummaryBaseAmount—The total amount of charges subject to taxes.
• insertInstlTaxSummaryAmount—The amount of tax applied to the base amount.
• insertInstlTaxSrvTaxTypeDesc—Tax Type Description as defined by the external tax service

Aria can now handle the application and unapplication of payments for installment surcharges, including a single payment or multiple payments in a single transaction. You can now unapply installment surcharge payments from voids, refunds, credit memos, and writeoffs including taxes, including full or partial applications.

Learn how to create an installment surcharge in the Aria Billing application.

New Financial Transactions Events to Support Payment Applied and Unapplied Events (DEV-11915)

This feature introduces four new events (952–955) under the Financial Transactions event class to notify when electronic or external payments are applied or unapplied, supporting lockbox and dunning processes. These events trigger for manual or automatic payment application/unapplication (except during payment creation—unless there are any unpaid charges—or voiding) and provide detailed payloads with impacted charge information.

A new event payload version (3.4) enhances XML, Name-Value Pair, and Email formats to include additional fields like charge transaction IDs and invoice details.

1. Calling move_payment_m API/UI (or via Accounts > Payments > Apply a Payment > Unapplied Payments > select a payment)

   Note: See related ticket regarding move_payment_m API.

2. Creating a refund with <apply_refunded_payment_on_refund_trans>=1 input (in issue_refund_to_acct_m API) and refund-related action=none or reverse line items with refund amount > reversal amount

1. Creating a payment when there are unpaid charges
2. Creating an Invoice (or any other charge like dunning charge, balance transfer, etc.) when there is an open payment
3. Voiding charges like invoices or refunds when there is another unpaid invoice/charge
4. Creating an Invoice-based credit memo when there is another unpaid invoice
5. Voiding an invoice-based credit memo causing that invoice to be paid when there is an open payment
6. Creating a refund with “open paid line items” option causing the unapplied payment to be applied on refund
7. Creating a refund not paid by a reversal, or by #6 above (refund with “open paid line items” option) or by <apply_refunded_payment_on_refund_trans>=1 (in issue_refund_to_acct_m API), then any available open payments will be applied on refund

   Note: If the payment being refunded is a “manual allocation type/perpetual payment” and that payment has an amount left to be applied, then it will be automatically applied to the refund being created.

1. Calling move_payment_m API/UI (or Accounts > Payments > Unapply a Payment)
2. Creating a refund with “open paid line items” option

1. Voiding a payment
2. Voiding an invoice/refund
3. Creating an invoice-based credit memo
4. Rebilling an invoice which internally creates invoice-based credit memo

To take advantage of these new events and data, submit a request to your Aria representative to update the parameter 'PROV_FINANCIAL_TRANSACTION_CLASS_VERSION_M' to 3.4.

Get Accounts Assignment History - Part 2 (DEV-11917)

A new Subscription Details form has been added to the Subscriptions > Details CCP page and connected to the Subscriptions > Billing Groups workflow. This form appears when a subscription is selected from the populated details list.

Partial Invoice Dispute and Write-Off at the Invoice-Level (DEV-11923)

This feature introduces partial invoice dispute and write-off capabilities, allowing disputes up to a 'disputable amount' at the invoice level for self-pay invoices. This enables precise dispute resolution, improves cashflow, and enhances customer satisfaction. Dispute allocation prioritizes unpaid invoice lines, with excess amounts unapplying payments based on a FIFO method, and backward compatibility ensures disputes specified with only the invoice number default to the full unpaid balance.

In this release, Aria enables this functionality via APIs (see API ticket) and, in an forthcoming release, will enable it via the UI.

1. The presentation in the Aria Billing UI of disputes now displays "Dispute Hold" rather than "Write Off," impacting these screens: Account Overview > Recent Transactions; Account Overview > Statements and Invoices > Transactions; Account Overview > Recent Payments; Payments; and Account Overview > Statements & Invoices > Invoices > select an invoice > Write-Off/Dispute Invoice link.
2. The create_writeoff_or_dispute_m API no longer returns a service credit as a separate line item. In addition, the <writeoff_transactions> array response is now sorted by sequential invoice line number.

Evertec Phase 2—Smart Payments Integration (DEV-11940)

In this release, Aria adds additional functionality to the Evertec Smart Payments integration. 

This includes supporting the following features: 

• Credit Card Payment Authorization (Online payments)—This includes the following supported card brands: 
  • Visa
  • Mastercard
  • American Express 
  • Diners Club International 
  • Discover 
• Credit Card Payment Capture/Sale
• 3DS-initial and final authorizations for supported card brands (Visa and Mastercard—pay_method =1) 
• Authorization reversals (reversing pre-authorizations) 
• Full and partial refunds for Credit Card payments 
• ACH payment support (pay_method = 2) 
• Tokenized ACH payment support (pay_method = 48)
• ATH payment support (ATH is an interbank network connecting financial institutions in Puerto Rico and the Caribbean—pay_method =50)
• Kount fraud scoring support for pay methods 1 and 13 (Credit Card and Tokenized Credit Card) 
• Transaction logging for all actions via the Evertec adapter 

Information on API-related enhancements for Evertec Phase 2 of Smart Payments can be accessed from here.

Enhanced Error Messaging Added for Stripe Smart Payments (DEV-11944)

Aria has updated its error messaging for the Stripe payment gateway as part of its Smart Payments integration. This applies to payment token generation errors and payment capture errors within the Aria UI for PCI-compliant payments as well as via Direct Post. The existing error message in the Aria UI will now include the processor error response (e.g., “Your card has insufficient funds.”) along with the notation “could not validate billing information.”

This applies to the following UI screens: 

• Payment Methods 
• Add/Edit Billing Group (Primary and Secondary payment method) 
• Payments 
• Add Plans (Primary and Secondary payment method) 

API-related enhancements for this feature are included from here.

Soft Failure Messaging Enhanced for Visa Card Transactions (Vantiv)(DEV-11946)

For the Vantiv payment gateway, Aria has provided more detailed soft failure messaging for VISA card transactions. Declined transactions will indicate if the transaction is not supported by the card issuer or if a transaction is blocked, which necessitates contacting the cardholder (mapped to two new three-digit VAP codes, which stands for Visa Analytics Platform). Also, the two existing Decline error messages will be mapped to a new “Do Not Honor” VAP code.

The three new response codes are as follows:

Buckaroo Smart Payment Enhancements for Tokenized Credit Cards, SEPA and iDEAL (DEV-11949)

Aria has enhanced its Buckaroo Smart Payments integration to support the following additional features:

• 3DS and non-3DS Authorization (Capture and Reversals for Tokenized Credit Cards, TCC-pay method = 13) 
• Refunds for TCC Authorization, Capture and Reversals Transactions (table)
• Recurring TCC payments with an Authorization token 
• Query token failure error message displayed in Aria UI 
• Transaction logging for the CC and TCC pay methods (also including the SEPA/Tokenized SEPA and iDEAL direct pay methods)

The following card types are supported for 3DS: 

• Visa
• Mastercard
• American Express 

Additionally, the 3DS Termination URL field has been added and can be accessed as shown (Configuration > Payments > Payment Gateways\Collection Groups > Processing Options tab):

The following TCC card brands support refunds for Authorization Capture/Reversals:

*-Tokenized Credit Card pay method

Buckaroo does not support recurring or subsequent authorizations using a token. As per Buckaroo CC flow, Aria supports the tokenized credit card payment method. Once a token is generated for a given card during the initial authorization, Buckaroo only allows recurring payments, not recurring authorizations, using the created token. If a subsequent authorization with the token from the initial transaction is attempted, the transaction will fail.

Error messaging has been enhanced for payment method creation failure to display the processor error response, as shown:

Aria has also implemented transaction logging for iDEAL and SEPA/Tokenized SEPA payment types, as follows: 

• Integrated transaction logging for iDEAL initial payment, query token, and refund (initial payment [pay method = 49] and recurring payment [pay method = 37]). 
• Integrated transaction logging for SEPA (pay method = 26) refund. 
• Integrated transaction logging for Tokenized SEPA (pay method = 37) query token and refund. 
• Integrated transaction logging to capture logs in both success and failure scenarios. 
• Integrated transaction logging to capture logs based on different logging types (FULL, SUMMARY, ERROR, NONE). 

Transaction logging has also been implemented for Tokenized Credit Card payments (Visa, Mastercard and American Express), as follows: 

• Integrated transaction logging for authorization, reversal, capture, payment, query_token, refund, and authorize_3ds actions. 
• Integrated transaction logging to capture logs in both initial and recurring transactions. 
• Integrated transaction logging to capture logs in both 3DS and non-3DS scenarios. 
• Integrated transaction logging to capture logs in both success and failure scenarios. 
• Integrated transaction logging to capture logs in all supported credit card types in Buckaroo. 
• Integrated transaction logging to capture logs based on different logging types (FULL, SUMMARY, ERROR, and NONE).

Information on API-related enhancements for Buckaroo Smart Payments can be accessed from here.

Compliance Support For Multi-Factor Authentication (MFA) (DEV-11956)

The following updates have been enhanced for Aria’s MFA (Multi-factor Authentication) to uphold security standard compliance:

• The MFA/Linus One-Time Password (LinOTP) behavior has been modified to ensure email tokens are updated regardless of the global param OTP_ENABLED status. If a LinOTP configuration exists, an attempt to update the token will occur.

• Password activation links containing special characters no longer result in a “Password Link Expired” message for first time users.

• Aria’s MFA now supports editing within the OTP code fields, previously you could not backspace out an already entered number when entered incorrectly.

• Being locked out from too many OTP code fails is now handled in a consistent manner for all users providing a better user experience.

All Service Rates List View - Part 2 (DEV-11961)

The All Service Rates workflow has been redesigned to be more intuitive and adaptable for larger data sets by implementing the following new features:

• The visual presentation and usability of the Add Custom Rates interface has been enhanced to better manage the positioning and visibility of elements as you scroll through Subscription and Add-on services. These changes ensure that the relevant data remains visible and accessible even when navigating through multiple service tables.
• The Service Rates table’s editable rows now allow “0” as a valid Rate Per Unit for tiers. Additionally, keyboard shortcut functionality has been enabled allowing you to use standard operations such as Ctrl+A (select all) and Ctrl+V (paste) within the Rate Per Unit input field.
• The Service Rates view has been enhanced with visual indicators for queued changes. A new icon has been added to highlight nodes with pending modifications, allowing you to quickly identify queued subscriptions. When hovering over these indicators, an informative tooltip appears providing details about the queued subscription change.

Account Status Update - Part 2 (DEV-11962)

The ability to delete queued account status changes has been added within CCP, improving flexibility in account management. You can now cancel scheduled account status updates if needed, which allows you to have more control over scheduled updates.

Level 2/Level 3 Payment Data Introduced for Braintree Smart Payments (DEV-11974)

Aria introduces new functionality in this release to control sending Level 2 and Level 3 data in the payment request to the Braintree payment gateway. As a reminder, providing Level 2 and Level 3 data enables costs savings for merchants because of lower interchange rates and lower transaction processing costs. 

To enable Level 2 and Level 3 transaction data, navigate to Configuration > Payments > Payment Gateways/Collection Groups, select Braintree and access Processing Options. Under Level2/Level3 Data Options, select Yes at Send Level2/Level3 Data in the payment request (default is No).

Also, the shipFrom_postalCode field has been added at the Advanced Options tab for Braintree Payment Gateway and Collection Group configurations. This field value will be included as part of Level3 data sent to Braintree during the payment request. 

Additionally, line items with a quantity of 0 will be filtered out when sending Level 2/Level 3 data to Braintree, as Braintree does not accept zero values at these fields.

Additional validations have been added for Level 2/ Level 3 data to Braintree.

Character limits have been added for the following string fields:

Decimal place limitations and other validations have been added for the following decimal values:

Additional Level 3 fields have been added for sending Level 2/Level 3 data:

Stampen Future Cancellation Failures (DEV-11981)

Subscriptions now consider queued changes scheduled on the anniversary date during invoice re-generation. When creating future cancellations, selecting invoices marked as “Complete” will revert the invoice status to "Pending". This status change allows future cancellation queues to be executed correctly during the re-generation of the pending invoices since invoices with a "Complete" status cannot be regenerated. This update applies to all the queued changes, including anniversary queues, and all discard cases, excluding void scenarios or existing pending invoices with queues.

Previously, when creating future cancellations, the subscription would not cancel and the customer would continue to be charged.

Evertec Added for Smart Payments (Phase 1 Basic)(API)(DEV-11471)

For the Evertec payment gateway, use the remove_acct_payment_method_m API to invalidate a token used for tokenized payments. Once the token is invalidated/deleted, the same token cannot be used again for future billing transactions. 

Invalidate/delete the token through the following API inputs: 

• <payment_method_no> where the token (<agreement_id>) is associated 
• <acct_no> for which the token is to be invalidated

NSO Installments Phase 8: Enhanced API Support (DEV-11912)

This phase of NSO Installments introduces enhanced installment support in the APIs edit_installment_term_m and get_installment_terms_m.

Aria has updated the behavior of the edit_installment_term_m API so, when updating an installment term, data passed will be updated while data not passed will retain their stored values.

New Financial Transactions Events to Support Payment Applied and Unapplied Events (DEV-11915)

This feature introduces four new events (952–955) under the Financial Transactions event class to notify when electronic or external payments are applied or unapplied, supporting lockbox and dunning processes.

In addition to the new events, this feature includes validation in the move_payment_m API to prevent simultaneous apply/unapply actions on the same charge, returning Error Code 1016 "Invalid input: unapply_trans_id and apply_trans_id cannot be the same" if violated.

Partial Invoice Dispute and Write-Off at the Invoice-Level (DEV-11923)

This feature introduces partial invoice dispute and write-off capabilities, allowing disputes up to a 'disputable amount' at the invoice level for self-pay invoices. This enables precise dispute resolution, improves cashflow, and enhances customer satisfaction.

In this release, the application enhancement is enabled and supported via these APIs: get_invoices_to_writeoff_or_dispute_m, create_writeoff_or_dispute_m, get_writeoff_details_m, get_acct_writeoff_or_disputes_m, and get_acct_trans_history_m. In a subsequent release, this will be enabled in the Aria Billing UI.

Aria returns the new error code 3119 "The input value in writeoff_dispute_amount field exceeds the invoice_disputable_amount." when the <writeoff_dispute_amount> amount exceeds the maximum allowable write-off/dispute amount.

Aria has altered the possible values returned in the <transaction_desc> output field in get_acct_trans_history_m: this transaction description might now be either "Write-Off #12345" (with the Aria-assigned write-off number) or "Dispute Hold" depending on the related scenario.

1. The presentation in the Aria Billing UI of disputes now displays "Dispute Hold" rather than "Write Off," impacting these screens: Account Overview > Recent Transactions; Statements and Invoices > Transactions, Account Overview > Recent Payments; Payments; and Accounts > search for an account > select an account > Statements & Invoices > Invoices > select an invoice > Write-Off/Dispute Invoice link.
2. The create_writeoff_or_dispute_m API no longer returns a service credit as a separate line item. In addition, the <writeoff_transactions> array response is now sorted by sequential invoice line number.

Evertec Phase 2—Smart Payments Integration (API)(DEV-11940)

As part of Aria's Phase 2 integration of Evertec Smart Payments, the following input parameter has been added to enable ACH payments:

This new input parameter has been added for the following APIs:

• assign_acct_plan_m
• create_acct_billing_group_m
• create_acct_complete_m
• create_order_m
• create_order_with_plan_m
• collect_from_account_m
• manage_pending_invoice_m
• settle_account_balance_m
• update_acct_billing_group_m
• update_acct_complete_m
• update_acct_plan_multi_m
• update_order_m
• update_payment_method_m

Enhanced Error Messaging Added for Stripe Smart Payments (API)(DEV-11944)

In addition to enhanced error messaging for token generation and payment capture errors added for Stripe Smart Payments in the Aria UI, error messaging has also been added for selected APIs. This includes the following: 

• For the update_payment_method_m API, the existing <proc_status_code> and <proc_status_text> output fields in the collection_info array will now return processor errors for the create token action. 
• The existing <proc_status_code> and <proc_status_text> fields will now return create token failures for the following APIs: 
  • create_acct_billing_group_m 
  • update_acct_billing_group_m 
  • validate_acct_fraud_scoring_m 
• A new <payment_method_proc_response> output array has been added to return processor errors during payment method creation failures, as follows:

This applies to the following APIs:

• create_acct_complete_m
• update_acct_plan_multi_m

Buckaroo Smart Payment Enhancements for Tokenized Credit Cards, SEPA and iDEAL (API)(DEV-11949)

Aria adds API-related functionality for the Buckaroo Smart Payments integration, noted below.

For Buckaroo Smart Payments, 3DS authentication-based authorization has been added. As noted above, the 3DS Termination URL setting is the Return URL option for the authorization in which the customer will be redirected after completing 3DS authentication.

The 3DS authorization is a three-step process:

The 3DS Termination URL setting (added as noted above) impacts the following APIs: 

• authorize_3d_secure_m 
• authorize_electronic_payment_m 
• update_payment_method_m

3DS Authorization is supported by the Visa, Mastercard and American Express card types. 

The <proc_status_code> and <proc_status_text> fields also now accommodate messaging for query token failure for the following APIs: 

• assign_acct_plan_m 
• authorize_electronic_payment_m 
• create_acct_billing_group 
• create_acct_complete_m 
• update_acct_billing_group_m 
• update_acct_complete_m 
• update_acct_plan_multi_m 
• update_payment_method_m

Also, to improve the clarity of error messages, the field now includes more detailed information if it is available from Buckaroo. If there are multiple error messages for a transaction, they will be concatenated and separated by a semicolon.

For example:

“491 - Validation Failure” has been updated to “491 - Validation Failure; Parameter ‘CVV3’ is empty.” 

“791 - Pending processing“ has been updated to “791 - Pending processing; C620 - Awaiting transfer to bank.”

Compliance Support For Multi-Factor Authentication (MFA) (DEV-11956)

The following update has been made to Aria’s Multi-factor Authentication (MFA) to uphold security standard compliance. When the create_user_m or update_user_m APIs are used to set or update an email address for a user, LinOTP will also be updated with the new email address used for sending login tokens.

Adyen Payment Token Processing Modified For Smart Payments (DEV-11989)

Aria has enhanced its Adyen Smart Payments integration by mapping the token generated from the <bill_agreement_id> to the shopper reference mapped to the tokenized pay method. This enables greater payment flexibility when applying multiple tokens across similar pay methods for the same customer.

This enhancement applies to the following APIs:

• create_acct_complete_m
• update_acct_billing_group_m

Assign_Custom_Acct_Plan_Rates_m Now Deletes Tiers When Modifying Plan Schedules (DEV-12009)

A new input parameter <custom_rates_directive> has been introduced to the assign_custom_acct_plan_rates_m API to allow you to modify the custom rate tiers to be fewer than the original custom rate tiers. Previously, the custom rate tiers could only be increased.

The <custom_rates_directive> parameter governs whether to remove the existing custom rates when assigning new custom rates. The default value is '1' and leaves the existing custom rates in place. A value of '2' will remove the custom rates and honor the custom rates passed.