Export page to Open Document format View page as slide show

Mobile Payment

Mobile payment

  • Payment conducted with mobile devices
  • Goals for payment systems
    • Security
    • Interoperability
    • Privacy
    • Global acceptance
    • Ease of use
  • All goals not required for all

Examples

  • Few categories of mobile payments
  1. Mobile P2P – mvia mexico, mPesa
    • Reimburse a friend, pay babby sitter, give kid sister pocket money via PayPal, …
  2. Mobile POS – BlingNation
    • Hardware oriented i.e. RFID, NFC, POS Readers
    • Chip credentials jump start the POS transactions – adoption barriers
  3. Mobile commerce
    • Buying item from mobile (browser/App) not desktop/notebook
    • Ovi, Windows Market place, iPhone store, Android market, Amazon, ebay, etc
  4. Mobile payment acceptance – PAYware Mobile, Android Square
    • Swipe attachment to your phone then use it to receive transaction payments

Mobile Electronic transactions (MeT)

  • MeT initiative formed in 2000
    • To facilitate the different types of mobile payments
  • Changed to MeT Ltd in 2002
  • Vision of mobile phone as Personal Trusted Device (PTD)
    • Ultimate digital wallet used for mobile transactions e.g. mobile wallet
    • App on mobile phone
      • Trusted storage holding tickets, payment Apps, receipts, discount cards
      • Support remote & local transactions
  • Needs security elements
    • Handle encryption
    • Authentication
    • Hold secret data e.g. pin codes, keys, certificates
    • Can be external hardware, software or ICC (intergrated circuit card, smartcards)
  • Currently focused on contactless payment systems based on NFC
  • Never materialised
    • Ideas used in other solutions e.g. google wallet

Mobile payment landscape (by MeT)

Payment environments

  1. Remote
  2. Local
  3. Hybrid (Proximity)
  4. Desktop

1. Remote

  • Distance between payment service & customer is longer
  • Connections done over network
  • 3rd party handles the charging
    • Service charge in phone bill
  • E.g. Apps
    • SMS or phone call based services - parking tickets, coke machines, ..
    • Browsed services – Internet shopping
    • Payment through bank account in Internet (netbank)
    • By giving credit card details (SMS or Internet)
    • In phone bill

2. Local (Proximity)

  • Services are in proximate distance of the customer
    • Coke machine, shop cashier, …
  • Services & payment accessed via local link
    • NFC, RFID, Infrared, Bluetooth, (WLAN)
  • No direct access to third party from terminal.
  • Numerous approaches
    • Prepaid accounts
    • Tickets
    • Electric money (bitcoin?)
    • payment cards

3. Desktop

  • Shopping done via desktop computer
  • Mobile phone used for payment
  • Special case of local payment

Mobile commerce process

  1. Connect the service
  2. Buying
  3. Paying
  4. Receipt

1. Buying

  • Process for customer to select what to buy
  • After selection customer states the will to buy the selected product
    • Customer is often identified at this point
    • Discount give to regular customer
  • At the end of buying process bill is delivered to the customer

2. Paying

  • Customer checks/verifies the bill & hopefully accepts it
  • Customer send his acceptance of the bill with the payment device to the service
  • Customer is charged
    • Loss of payment ticket
    • Money taken from account
    • Charging order sent to 3rd party

3. Receipt

  • Receipt is delivered to customer
    • Either in paper / electronic form
  • Verification of the transaction event

Electronic commerce modelling language (ECML)

  • IETF effort to standardise the notation used for payment information
    • v 1.1. defined in RFC 3106
    • v 2 defined in RFC 4112
      • Released June 2005
      • RFC 3505 defines requirments for ECML v2
      • Update to v 1.1
    • XML based
    • Allows compatibility between different systems
      • Helps the customer

Payment types

  • Before hand
    • Tickets, accounts (for customers)
  • During transaction
    • Accounts (for service provider), credit card (for service provider)
  • Afterwards
    • Billing, credit cards (for customer)

Mobile tickets

  • Ticket – a proof of right to use or access a service
  • MeT defined two types of mobile tickets
    1. Virtual tickets
    2. PTD tickets

1. Virtual tickets

  • Proof/ticket resides at ticket's issuers server
  • Ticket redemption requires user authentication
  • Requires connection to the ticket issuer's server at the use time
  • Acquisition of ticket does not require any object download to mobile device
  • Mobile device requires ID certificate acceptable by service provider
  • Physical e.g. SIM
  • Downloadable certificate
  • Stored at mobile wallet
  • Ticket use
  • Mobile device ID delivered to service
  • Service connects to ticket service & verifies the right of use

2. PTD tickets

  • PTD tickets
    • Ticket resides at the mobile device
    • Possesion of the ticket is proof enough
    • Ticket downloaded from ticketing server
      • Certificate
    • Whole ticketing App downloaded e.g. Java program
  • Ticket use
    • No connection needed to ticket issuer
    • Ticket is uploaded to the server
    • Requires secure handling
    • Prevent copy, multiple use
    • Single use tickets Vs multiple use tickets
    • Tamper proof
    • SMS tickets used for busses & trams in Helsinki

Lot of solutions in the market

  • Big players
    • Creadit card companies
    • Banks
    • Mobile phone companies (nokia wallet), google, apple (iwallet coming?), …
  • Lot of local approaches
    • Shopping chains own solutions
    • cafeteria cards
  • Alternate currencies
    • Bitcoin, dogecoin …
    • prepaid phona call time.

Considerations

  • How is my service used?
  • Can I charge from the use of the service?
  • Whats the best way for customers to pay for the service?
  • Do I need to have contracts with 3rd parties for billing?
    • Mobile operators
    • Credit card companies
  • Whats the overhead cost from the payment system to the service?
  • Closed or open payment system?
    • Can tickets we sell be used only in our services? or
    • Should we provide world wide compatibility?

Resources

Last modified: 2014/04/22 08:53