Payment Management : Public <<TMF_AF>> Aggregated Function
The Payment Management function is aimed at processing all payment flows issued or received by the Enterprise:<br/>• Regardless of the payment method (address all payment methods supported by the Enterprise), for example a cash payment or a payment with loyalty points to buy an accessory, a payment on invoice to pay the subscription, a payment via a scheduled plan to buy a device<br/>• For prepaid as well as post-paid offers.<br/>• Immediate payments are also recorded (for instance for offer including equipment or terminals sales)<br/>• it also includes management of deposits related to orders.<br/><br/>It comprises the main following sub-functions.<br/>Payment flow management which role is to:<br/>• Manage all of the relations with the banking sector (unique portal), both outgoing (direct debit requests, payments by credit card, refunds by cheque or by bank transfer, etc.) and incoming (for example for bank transfers and cheques files, payment rejections, etc.) for customers,<br/>• Manage all flows related to banking (supervision, management of bank opening schedules) and allow a rapid response in the case of problems.<br/>It includes:<br/>• Formatting of the orders: to the 3rd party systems for outgoing payments (depending on the Electronic Funds Transfer (EFT) agreements with banks or other 3rd parties: e.g. Electronic Data Interchange (EDI) message) and to the originating systems for the incoming payments,<br/>• Grouping and ordering of orders (e. g. group payment requests by target company and source company).<br/><br/>It handles both outgoing (mostly payment requests, occasional refunds), and incoming events (payments or rejections).<br/>• Payment management<br/>This functionality handles the business logic needed to perform a payment request that can require on-line interface with the banking system. It addresses use cases such as :<br/>1. Payment request to top-up prepaid balance / account<br/>A payer wishes to pay on-line for a prepaid account top-up (payer may be the account holder or not),<br/>2. Direct Payment related to a customer order (on-line or in shops) : sale of a device, or deposit for a rented device<br/>3. Payment request to settle a debt.<br/>A payer wishes to pay for one invoice (main case), or a subset of an invoice (partial payment).<br/>• Payment tractability and banking reconciliation<br/>Generically, the payment functionality should involve tracing and querying capabilities that allow to trace back incoming payments to the originating event (outgoing payment request or invoice). A payment can be partial.<br/>• Payment recycling / re-allocation<br/>Depending on the implementation of interfaces with banking or other 3rd party systems, it may happen that incoming payments are received with ambiguous data, i.e. cannot be traced back with certainty to an originating event. In this case, a recycling functionality is needed.<br/>
- Associations To
- Associations From
- Tagged Values
- Advanced
- Other Links
Tag |
Value |
FunctionID |
3.7.1.2 |
Details:
|
HierarchyLevel |
2 |
Details:
Description: the level of this object in the hierarchy (1-x integer)
|
UID |
112 |
Details:
|
Property |
Value |
isFinalSpecialization: |
0 |