ECE Allows Multiple Refunds Resulting in Revenue Leakage in SMS Refund Scenario
Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 11.2.0]
Information in this document applies to any platform.
On : ECE 184.108.40.206.0 version, Rating business logic
Consider a SMS Charge Offer of 4USD/SMS. Customer Balance is 4 USD.
1. Perform SMS Debit request, see that it is a success. Account balance should be deducted as per SMS Charge offer (charge is 4 USD )
2. Perform SMS refund request with refund information of SMS Debit request of step 1, see that it is a success. Account balance should be credited as per SMS Charge offer ( 4USD )
3. Perform SMS refund request again with same refund information of SMS Debit request of step 2. It returns 4USD. Now balance become 8 USD instead of 4 USD.
Note: In Step 2 & 3, passed same session id
4. Perform SMS refund request again with same refund information of SMS Debit request of step 2 with different session Id. After this refund, account balance becomes 12 USD.
In Step 3 & 4 it is allowing to do SMS refund request for same refund information and crediting customer balance which is not expected.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms