2. mobiquitymobiquity
Mobiquity - mCommerce Anekantavada ( Subjectivism )( Subjectivism )
Reality is perceived differently from different points of view, and that no single point of view is completely true.
Project Sponsor View
OR
Organizational View.
Value model / Segments of eCommerce.
Commercializing Ng mobile VAS Services
Business & System Models.
Project Implementation View Customization for specific Processes .
Client Applications integration
Functional Product
Requirements View
Universal Value
Money , Credit , Virtual Value ,eXchangeable items
Building Blocks Services - OMG standards
createPayment , createOrder , postGL , createParty
Domain Services
Hospitality , Digital Business , Travel , Finance.
Technology View Software Framework & Infrastructure Architecture.
Support for Various UI Modes.
Support for Partner Services Integration for “Functional
Operations View ( Security )( Security ) Executive BI and Reporting
Partner Revenue Agreement / Settlement
OSS &Customer Care
Banking & Legal View Partner Banks Perspective.
Clearly Defined Information Rights
3. mobiquitymobiquity
Organizational View What eCommerce mean to them ?
Organizations Most “Value segment”. [ Check Relevant Modules ]
Electronic retailers
Electronic catalogues (e.g Yellow Pages Filtered by M-Wallet
Users)
Electronic supplier & procurer networks
Electronic notification system ( Stocks etc. )
On-line auctions & Reversed auctions
Commercializing Ng mobile VAS Services
Get Paid Ng mobile Service
Pay Ng mobile Services.
Business & System Models of Ng mobile VAS Services.
Business Models
System Models.
Business & System Model Integration
For Business Model -> System Model should provide ways to
achieve Business Objective.
4. mobiquitymobiquity
Organizational View Commercializing Ng mobile VAS Services
Subscribers “Get Paid “ in MobileWallet
Using Advertising Services
Coupons from Vendors
Using ‘Sponsor Ringtones’
Taking Surveys
Referrals
Calling Back…
On-line auctions & Reversed auctions
Commissions
Subscribers “UsesMoney“ in MobileWallet
Mobile TopUp.
Pay Utilities
Transfer M-money
Pay Digital services
Pay services (Travel services : Riksha )
Courtesy : ???? Need to create
5. mobiquitymobiquity
Organizational View OMG eCommerce Base Business Models.
Retail Point of Service (POS) -
Person is paying using either an attended (clerk at check-out counter), or an unattended
terminal at a merchant’s place of business (self-serve gasoline and grocers)
Person is paying using a remote terminal that is not under merchant’s control (Amazon,
JC Penny Catalogue, e-payment for taxes)
Bill Payment – Consumers pay a business for a “work for hire” (landscaping), subscriptions
(Comcast, AOL), utilities (electricity), insurance
Remittance information required
Payment & Penalty schedule required
Person-to-Person payments (no business involved)
Direct funds transfer (Wire transfer, Western Union)
Indirect funds transfer (credit card, money order, travelers checks)
Commercial Payments
T & E – requires requires supporting details (hotel bill, restaurant receipt)
Purchasing card – requires remittance information and approval authorities
Purchase order payment – requires contract, remittance information, approval
authorities, delinquency fees
6. mobiquitymobiquity
Organizational View Base System Models
System Models
Systems and services to be explained by each of the models
Payment devices – e.g., Wireless – PDA (IR), Phone (RF or IR) , Proximity (RF); Wired –
Magnetic Strip, Chip, Key Terminal, electronic check
Authorization, Clearing & Settlement operation for payment
Authentication of payor and payee
Micro payments (Macro are covered in the SWIFT model)
Payment accounts – checking, savings, revolving charge, credit cards, cash advance
Different Access Models, Trading Models, Security Models, Payment Models
Business & System Model Integration.
For Each Business Model , System Model should allow achieve Business Objective
Define ‘Template System Process’ combining ATCP models interactions
Define Strategy for BaseSystemModel which gets subClassed for every Business
Model.
7. mobiquitymobiquity
Client Project Implementation View Process-Driven Approach
Bank Travel Site
Payment
GatewaySDP
E-CommerceAccounting
Order
s
Telecom OSS
Design
Process
Definition
Execute
Analysis
Change
Monitor
Information IntegrationInformation Integration
Enterprise Service BusEnterprise Service Bus
ITIT
BusinessBusiness
Transaction
Execution
Business Process ManagementBusiness Process Management
SOA GovernanceSOA Governance
MetadataMetadata
8. mobiquitymobiquity
Project Implementation View Customization eCommerce
Model Client
Business
Map Business Processes
Core Business Services ( Order etc… )
Select Business Composite Applications
Set up Books of Accounts &GL
Business Simulation & Mock
Runs
Use Jmeter Based Load testing.
Design the Systems & Identify
Gaps in Functionality
Implement the Systems by
Customization – Rules and Process additions
Adding Business Applications
Test & Deploy Systems
BusinessArchitectITArchitect
9. mobiquitymobiquity
Project Implementation View eCommerce Project Cycle
Model Client Business
Using Standard Processes
defined by Standard bodies like
ebXML
Map Business Processes
Check existence of Process
Models in Mobiquity eCommerce
Customize eCommerce
Use Customization Points to
make software adaptation for
Client needs.
Define new applications on the
platform using Mobiquity tools.
Achieve Integration with
Partners & Client Apps using
MEPs.
Client Appl integration e.g. CMS
By Data Replication
By Service Integration
Ecommerce Project Cycle
Model Business
Requirements
Model Current
State
Project Team
Training
Project
Planning
Map to Ecommerce
Functionality
Develop
Custimazations
if necessary
Build
Appropriate
Interfaces
Design and
Develop Data
Conversions
Integration
Testing
Acceptance
Testing
Use Simulations
For Visualization
Post -
Implementation
Support
End User
Training
Identify Gaps
Design
Solutions
Future
State Design
Iteration 2..
Iteration 1
17. mobiquitymobiquity
Technical View Building eCommerce Framework
Make it look Challenging
General Frameworks:
OMG eCommerce Domain Specifications
ebXML Technical Architecture,
MPEG-21 & IMPRIMATUR Business Model,
Trading Models:
Ad Hoc Functional and Process Models,
Global Commerce Initiative & Protocol,
Internet Open Trading Protocol (IOTP),
RosettaNet,
Secure Electronic Market Place for Europe (SEMPER)
Payment Models:
Electronic Payment Technologies,
Secure Electronic Transaction (SET),
TC 224 Report on 'Card-related secure commercial and financial transactions
Security Models: eEurope Smart Card Charter’s Global Interoperability Framework
Mobile commerce Models: OMA (MeT)
Web Services Architectures: Various Standards
Make it look Easy
Open Source Frameworks: Ofbiz ; Amexdes
18. mobiquitymobiquity
Technical View Mobiquity Technical View
Mobiquity Architecture
A. Mobiquity Access Models & Mechanism
B. Mobiquity Composite Business Apps
C. BTSL Reusable Components
D. Enterprise Service Bus
E. Payment Models for Integrating with Payment Gateways
F. Trading Models ???
G. Security Models ???
H. O&M Integration Models.
I. Client App Integration Pattern Models – Jencks
Mobiquity Payment Processing
A. Get Mobile Wallet
B. Shop with Mobile Wallet
C. Mobile Shopping -- “CNF” transactions.
D. Mobility Security & Fraud Detection
E. Mobility Payment Settlement
F. Mobility Transaction Management
.
22. mobiquitymobiquity
Technical View Mobiquity Architecture
A. Mobiquity Access Models & Mechanism
SMS
USSD
IVR
A. Mobiquity Composite Business Apps
Wallet Manager
Encrypted Storage ; Multiple Security Checks.
Subscription Manager
Registration & Lifecycle ; Multiple classification.
Commission & Tariff Manager
% charged on subscription
% charged on different kind of transactions
Configurable min / max value per transaction
Rules and Fraud Manager
Depending upon the transaction limits for the particular entity
Depending upon the anti-money laundering limits
Depending upon the available account balance of the particular entity
23. mobiquitymobiquity
Technical View Mobility Architecture
C. BTSL Reusable Components
Multiple Payment Adaptors
Payment Gateway Adaptor
ECS / EFT
Google CheckOut / Paypal
Multiple IN telephony adaptors
Eriksson
Siemens
Order Processing
Party
Accounts ( Ledger )
D. Service Bus & Customization Language
Rules
Customer can define Rules in Custom XML file
Customer can define condition for rules to fire
BPEL
Customer can customize the process flow.
24. mobiquitymobiquity
Technical View Mobility Architecture
E. Multiple Payment Gateway Adaptors
Banks & Credit Card Companies
Payment Gateways
E. Trading Models
F. Security Models
G. O&M & Support
Web Tools
Configure Thread Pools
Import / Export Customer data from Legacy database
E. Client Integration
25. mobiquitymobiquity
Technical View Mobiquity Payment Processing
A. Mobility Wallet Registration
User Registers with Mobility Wallet
Using Voice
Using Web
A. Mobility Service Registration.
Operator configures which services can be paid
using Wallet
Configures Payment Type since multiple
payment methods available.
Configures rules for limits for customer
seqment
C. Mobile Shopping -- “CNF” transactions.
D. Mobility Security & Fraud Detection
TBD
C. Mobility Payment Settlement
TBD.
C. Mobility Transaction Management
26. mobiquitymobiquity
Banking View Banking Money Flow between Parties
Customer/Cardholder
Bankcards and Issuers
MasterCard and Visa cards are sometimes known as
bankcards because individual financial institutions issue
them, banks for example, instead of the credit card
company itself, such as American Express® or
Discover®.
If the financial institution (or issuer) accepts the
customer's application, it issues the Visa or MasterCard
card.
The card may be a credit card, which means that the
bank has authorized a line of credit from which the
customer may draw;
or a debit card, which is tied to the amount of money
actually on deposit for the customer,
or a commercial card, which is used for business
credit charges
Merchant
Meanwhile, you or your business has opened a Mwallet
( bankcard transaction deposit account ) with your
bank, and your business has been approved for card
acceptance.
You are an authorized to acceptor of cards for the
payment of goods and services.
Courtesy : Global Payments
27. mobiquitymobiquity
Banking View Transaction Process Models( BPEL ? )
Authorization and Electronic Data Capture
Capture Card Details - Card number, expiration date, and counterfeit detection value
YCS then electronically routes the electronic data from the card to the card issuer.
The card issuer checks the cardholder account status, and the requested authorization amount is compared to
the cardholder’s available spending limit
The card issuer reviews with fraud protection tools. If the card is approved, the issuer posts the approved
amount against the cardholder’s credit line and the card issuer provides the authorization approval. At this
point, the authorization response is returned by the card issuer to the merchant and routed through YCS , the
processor.
Funding
The process of moving the funds from the cardholder’s account to the merchant’s account is called funding.
During funding, the issuing bank credits the merchant’s account with the amount of the transaction.
The merchant deposits the transaction receipt with the merchant’s bank.
The draft is routed to the cardholder’s issuing bank, which debits the cardholder’s account and sends the
cardholder’s monthly statement for payment.
Settlement
The process of moving the transaction information from your business to the cardholder’s financial
Institutions is called settlement.Visa & MasterCard maintain authorization and settlement networks for
bankcard processing and charge a fee for their use. This is transaction percentage, and this is the foundation
for discount rate.
Chargeback
Discount
Retention of Order Transaction History
29. mobiquitymobiquity
Banking View “Card Not Present Transactions”
Card Not Present transactions are those that occur when there is no face-to-face contact with
cardholder. It includes purchases made:
By Mail ( Mail Order/MO/TO) or By Telephone ( Telephone Order/MO/TO) or By Fax
Over Internet (E-Commerce) or Over Wireless & Voice ( referred to as M-Commerce and
V-Commerce )
Card Not Present Process Flow :
Get subscriber Information
cardholder's name, card account number & expiration date
the cardholder's billing address and zip code. ( for Authorization.)
Request the three-digit card authentication number (CVV2/CVC2/CID) from the signature
panel. ( 4 digit for American Express )
Make sale on signature as TO (telephone order) or MO (mail order).
Provide a copy of the ecommerce transaction to the cardholder, either with the cardholder
order (if being shipped to the cardholder) or separately (i.e. if purchase is a gift).
The transaction date is the date services / goods were shipped to the cardholder.
Electronically printed sales receipts provided to cardholder should truncate or mask
the account number
36. mobiquitymobiquity
Operations View Security Enhancements
Web Application Security
Login ID and password authentication
IP address authentication
Time of day and days of week based login control
Role based authentication
HTTPS for secure transmission
Forced password change every n days
Forced session idle timeout
Each transfer has a unique transaction ID
Transaction ID sent to IN for reconciliation
Periodic balance checksum
Automatic and manual transaction rollback provided
37. mobiquitymobiquity
Legal View eCommerce Law
What is “common” information?
What information can pass thro wire Transmission amenity
What information both trading parties can interpret
Security with SSL and Private – Public Key infrastructure is reasonable.
How to handle information in changing contexts?
? Who decides and what jurisdiction does the Changing Law gets interpreted.
? Validity of future laws to be binding for both parties; any safeguards for
withdrawal from contract in case of discriminatory laws.
Who own the information?
Owing Information can give full or partial rights to use, perform Business
Analysis, sell full , partially or aggregated values etc. Architecture should be
capable of switching Permissions to ownership ASAP with Law.
Who controls the information?
What communication mechanism needs to be inbuilt for fraud mitigations.
Who quality-controls the information?
Mandatory Requirements for storage
Mandatory Requirements for Transmission and level of encryption.
Process Framework for both automated and manual intervention.
What ensures information is available, accurate & of the “required” quality?
Enforcing Rules Updates from VISA & Government etc.
The same capability is being strongly reinforced by the current trend to service oriented architecture. As the back end enterprise applications are being broken up into components called services which can more easily be recomposed using information integration and service bus technology. This gives the agility to quickly produce new composite applications without resoring to programming, but it does not bridge the gap without the Human BPM.
The full cycle of business process management involves process design, and ultimately process analytics.
And to keep control on all of this, there is SOA governance to store and track and control all the pieces.
