Get Started. It's Free
or sign up with your email address
Rocket clouds
Aircell FSO by Mind Map: Aircell FSO

1. Store and Forward

1.1. Store based on Rev ByPass, requires ESB and portal running

1.2. AMS, is ACPU based, data stored in Oracle dB

1.3. RSA encrypted data

1.4. Requirements

1.4.1. PCI requirements

1.4.2. Reusable component for Refund oriented

1.4.3. Declined Auth's are written off via reconcillation component at end of graph

1.4.4. MOR Purchase defines a status depending on business rules

1.4.5. Strip the card info from the revBP dB and mark transaction as flushed

1.4.6. Purchase date populated as store date

1.4.7. Activation date populated as forward date

1.4.8. SLAs

1.4.8.1. Settlement within 48/72 hours

1.4.8.2. Scheduled at low time

1.4.8.3. Driven by Oracle storage

1.4.8.4. Create Workflows for each store and forward event

1.4.9. Decouple payments from diseMP, front loaded payments. Phase ++

1.4.10. GoGo WebService call hosted in ESB

1.4.10.1. Delayed playback of BPOE WebServices

1.4.10.2. Complete and Confirm Order based

1.4.10.3. Fixed Product defined

1.4.10.3.1. If blank, fetch default product

1.5. Sales Channels

1.5.1. POS

1.5.2. MSP

1.5.3. Enterprise

1.5.4. Video

1.5.5. Ground

2. Refund Automation

2.1. Scanning Refunds

2.2. Care oriented funds

2.2.1. Intention to automate the current process

2.2.2. Care create a refund diseMP workflow

2.2.2.1. Workflows are either auto approval or assigned to supervisors as per standard diseMP workflow

2.2.3. Possible for LAE to create a batch of workflows

2.2.4. LAE polls diseMP dB for approved workflows. Workflows will contain the POSREF for the transaction to refund

2.2.5. LAE will validate the refund

2.2.5.1. Validate the POS transaction

2.2.5.2. Validate the number of refunds against the POS transaction, by validating the Purchase MOR

2.2.5.3. Extract the TxRefNum for the POS transaction by using the PaymentID (ACLLIVE) and extracting the TxRefNum from the joined OneOffTxNum

2.2.6. Generate the batch refund XML as per Orbital XML Spec. The transaction type is NewOrder with substype of Refund using the TxRefNum

2.2.7. PGP encrypt the XML using the ChasePaymentech public key

2.2.8. SFTP the .pgp file to the Orbital Gateway

2.2.9. Poll the Orbital Gateway for the response

2.2.10. decrypt the rsp.pgp using the MDS private key

2.2.11. Process the refunds

2.2.11.1. Generate a refunded Workflow

2.2.11.2. Add the SLA to diseMP. NOT REQUIRED!!

2.2.11.3. Update/Confirm the care approved workflow adding a note on the status of the refunded transaction

2.2.12. Promo based refunds

2.2.12.1. Workflow Generation for Promo refund

2.2.12.2. Questions for care on promo types

3. Deferred Recognition

3.1. Linked to MSP NonCMP

4. Product Centre Mediation

4.1. SOAP UI WSDLs

4.2. Pull Data from Product Centre dB for full rule set

4.2.1. Schema definitions and aggregation SQL in LAE into denormalized EDW table

4.3. Extra attributes for product centre

4.3.1. Account Code, Marketing Codes and NominalNumbers for RevenueShare.

4.4. Pull model from EDW v's push model via the LAE

4.5. Require bulk upload mechanism for publishing video into ProductCentre

5. MSP Non CMP

5.1. Linkage of Packages/Services for Monthly Subscription

5.1.1. Need to look at defined MSP packages

5.1.2. Find the PoS service and recurring service part

5.1.3. Fabricate the POS transaction for each month

5.1.4. Tie the cash receipt to the MSP

5.2. Decomissioning the MSP provisioing and cash collections jobs

5.2.1. Phased approach to porting from diseMP billing to LAE oriented billing

5.2.2. LAE will invoke the Complete Order and Confirm Order for the recurring part of the MSP or alternative is to have LAE generate the batch XML as per refunds.

5.2.3. Action: Complete HLD Sequence flows

5.3. Creation of the MOR based on join of the Inv Detail and SubPurchase

6. Tax Reporting

6.1. On hold until business requirements are captured

6.2. ADP Taxware is capable of calculating tax in realtime

6.3. Issue surrounding the user meta data captured during portal puchase path. The portal has removed the billing data and currently there is no AVS checking involved.

6.4. MSP Taxation Rule Defn

6.5. Link Address Data for Taxation