Business Ecology Initiative & Service-Oriented Solution

Michael Poulin

Maestro, Visa and Service Orientation

user-pic
Vote 0 Votes

Recently I receive a note from HSBC about replacing my Maestro/Mastercard debit card by the debit card from Visa. The note explained that the reason for this was new feature for cardholders - ability to use their debit cards worldwide (Maestro has limited acceptance, mostly in the UK). Such HSBC care came as a surprise especially during the crisis and weak pound, i.e. when Brits have minimal interest in travelling abroad. So, I have not believed HSBC that the mentioned feature caused a dramatic campaign of card replacement. It is dramatic because the biggest UK financial institution has changed its debit card partner to its competitor - from Maestro/Mastercard to Visa.

Apparently, I was involved in some technical events last year that, I can suspect, were a part of the HSBC decision to change the partner. Here is a short story.

A few years ago Maestro/Mastercard and Visa developed new technological solution and procedure for authentication of cardholders that was supposed to prevent payment fraud via Internet. I will not overload this post with technical terms but can say that specified procedure required all merchants who accepted payments with debit cards via their Web Sites to include special formalised dialogs into their Sites. The dialogs had to help submitting secured passwords known by the cardholder and the card-issuer (bank) only to the card issuer fro verification of cardholder identity. The cardholder had to subscribe to this protection programme up-front. If submitted secured passwords matched the information kept in the bank, the debit card payment was approved, otherwise - denied.

'What's wrong with this?' you may ask. This is a great thing if we can protect cardholders. Yes, may be, but it protects the card-issuer (bank) first of all from the claims about unauthorised use of the debit cards (not necessarily stolen but used by the household members, e.g. kids). Still, it is not a problem.

The real problem is in that the card processing intermediary/organisations (acquirers), being under the pressure from Maestro/Mastercard, started to threat merchants with fees if they did not support this programme, i.e. did not modify their Web Sites and included authentication dialogs. At the same time, Visa offered its protection programme, actually, very similar to the Maestro/Mastercard one, but did not make it mandatory for the merchants.

What is the difference? Let's look at this case from the merchant perspective. The merchant has to: 1) modify and redeploy its Web Site which is not that simple thing for small and medium size organisations; 2) the merchant's Web Site should be open into uncontrolled (by the merchant) Web infrastructure used by the banks for user authentication procedures, i.e. merchant's Web Site got unmitigated risks of crash, delays, and whatever attacks; 3) cardholder easily forget the secured passwords and were not able pay, i.e. were not able to buy goods; this is direct negative impact on both merchant business and consumers.

Why all these happens? Because a company that offered a service to its customers - cardholders and merchant - decided to dictate or manage them. This company was overwhelmed with problems around debit cards, the problems that were recognised from the beginning, included into the Service Level Agreements and even covered by card maintenance fees (or whatever this fee is called). Do not you recognise a classical application-oriented behaviour? Applications used to dictate its consumers what and how to do and exposed its internal problems and constraints onto the users.

In the service oriented environment such behaviour is impossible. It is the consumer/user/client decides if offered service is good enough for the consumer's needs. If the service violates SLA, it is enough reason to switch to another service or provider. I think that HSBC thoughtfully or intuitively performed the service-oriented solution for its customers. I think this is a great example of the business action conducted in the service-oriented manner. Indeed, if a cardholder with Visa debit card does not want such protection, s/he can skip all associated burdens; if s/he wants it, s/he will push merchants to support the programme where needed.

So, being in the service business, serve. This is the SO business rule number one.

No TrackBacks

TrackBack URL: http://www.ebizq.net/MT4/mt-tb.cgi/15429

Leave a comment

Business and Technology ideas, concepts, methodologies and solutions leading to Service-Oriented Enterprise - the primary instrument for obtaining business objectives in fast changing environment

Michael Poulin

Michael Poulin is an enterprise-level solution architect working in the financial industry in the UK and USA.

He specializes in bridging between Business needs and Technology capabilities with orientation on business and technical efficiency, scalability, robustness and manageability. He writes about service orientation, application security and use of modern technologies for solving business problems. Michael contributes to OASIS SOA standards as an Independent Member; he is listed in International WHO's WHO of Information Technology (Historical Society) for 2001. View more

Subscribe

 Subscribe in a reader

Recently Commented On

Categories

Tag Cloud

'Navigating the SOA Standards Landscape, abstraction, active service, ADM, adopt changes, aggregate service, AIA, analysis, API, application, Application Integration Architecture, Architect, architect, architectural mission, architecture, Architecture, architercture, B-SOA, BAWG, BEI, Best Practice, bottom-up, BPEL, BPM, Busienss, busienss case, Business, business, Business Architect, Business architecture, business architecture, Business Architecture, Business Architecture Working Group, business concerns, business data, Business Ecology, business efficiency, business model, business operational model, business organisation, Business Platform Division, business process, Business Process Designer, Business Requirements, business risk, business service, Business service, Business SOA, business value, business view, business-centric, Business-IT problem, capability, CBDI, CBM, choreography, Cloud, Cloud Computing, COBA, collaboration, Collaboration, collaboreation, commodity, component, composition, concept, Conciliator, consumer, COSMIC, cost, cost estimate, cost of ounership, cost of ownership, crisis, CRUD, culture, Cutter Consortium, data ownership, data service, data store, DDD, decision logic, decomposition, demand, design, Design Pattern, development, domain, Domain, Domain Aggregate, Domain Events, Domain Service-Oriented Modelling, DOSOM, DOSOSM, driver, Dynamic Process Edition, EA, EDA, efficiency, end-to-end, Enterprise, Enterprise Architect, Enterprise Architectural Framework, enterprise architecture, Enterprise Architecture, ERP, ESB, event, Event, execution context, Execution Context, expertise, failure, feature, Flexibilit, flexibility, FPA, FSM, Full Functional Points, Functional Points, functionality model, future, Gartner, Governance, governance, granularity, harmonization, Healthcare, IBM, identiy credential, IEEE 1471, IFPUG, implementation, intangible value, Integration-Oriented Architecture, intent, interface, interface orientation, IOA, IT, IT Architect, IT Operation Support, IT organisation, IT without the IT Department, ITIL, Ladder to SOE, leasable Cloud, lease, Loose coupling, Lost in Translation, Management, Manifesto, market, MDA, Michrosoft, Mike Rosen, model, Model-Driven Approach, modelling, Navigating the SOA Standards Landscape Around Architecture, navigation, OASIS, OASIS SOA RA, OASIS SOA RAF, OASIS SOA Reference Architecture Foundation, OASIS SOA RM, ODBC, OMG, ONA, OO, Open Group, Oracle, orchestration, organizational change, participant, pattern, policy, principle, principle of separation of concerns, principles, priority, Private Cloud, Process, process, process-oriented, process-orineted, process-service, project, Provisioning, Pub/Sub, Public Cloud Busienss Requirements, QCon, RA, Real World Effect, Real World SOA, Referemce Architecture, Reference Architecture, Reference Architecture Foundation for SOA, Reference Model, Registry, rent, rentable Cloud, Repository, reuse, RIA, risk, RM, ROI, RPC, rules engine, RWE, SCA, scalability, security, service, Service, Service Autonomy, Service Composability, Service Contract, service contract, service description, Service Description, Service Discoverability, Service Execution Context, Service Orientation, service orientation, Service Oriented Enterprise, Service Relative Autonomy, Service Reusability, Service Separation of Concerns, Service State Management, Service Statelessness, service-oriented, service-oriented eco-system, service-oriented enterprise, Service-Oriented Enterprise, service-oriented environment, ServiceContract, seven properties that differentiate emergent architecture from the traditional approach to EA, situational, sizing, SLA, SO, SO environment, SO Principles, SOA, SOA Manifesto, SOA standard, SOA-RAF, SoaML, SOBA, social networking, SOE, SOEA, solution SOA, SOMA, Spring, standard, study, Summit, supply, T-SOA, tangible value, Technical Architect, Technical Architects, Technical Architecture, technical capabilities, Technology, technology, The Open Group, TOGAF, TOGAF 9.0, top-down, UI, UI Mediator, use, Value Chain, Value Network, Value Networks, view, view model, viewpoint, vision, VPEC-T, Web, Web Service, Web Services, WebSphere, WSDL, ZapFlash,

Monthly Archives

Blogs

ADVERTISEMENT