Beckn: UPI for Mobility & Commerce

Last week I wrote about Apple App Store turning itself into a gatekeeper. App Store ideally should have been a gateway for developers to reach out to iOS users and vice-versa.

Beckn enabled Open Playground v/s Traditional Monolithic Architecture

Key Features

Beckn Sector Specific Schema Extension


Interface between Beckn Apps and Beckn Providers
  1. Back-end process,
  2. Request Relaying: One of the several gateways act as an interface between Beckn Apps and Providers to relay requests.
  3. Supply: Beckn Providers make their services available on the network.
  1. Discovering: She would try to browse through menus of different restaurants. The restaurant would be registered as a Beckn Provider. Technically, the request is broadcasted through Beckn Gateways as intent and is received by the Beckn Providers who supply products or services.
  2. Discovering: Restaurant, a Beckn Provider, would respond with menu items in a schema (data arranged in a standard way to make it easier for both parties to communicate).
  3. Ordering: Once the user selects an offering, she would go ahead and try to place the order. This time also there would be a request to Restaurant followed by a request to another Beckn Provider with Payments Solution.
  4. Payment: Payment Solution would send the payment status response to Restaurant, which will interface with Delivery Service Provider.
  5. Fulfilment: Last, but not the least, UX at your end would interface with the Delivery Service Provider until your order is delivered.

Use Case: Mobility

Photo by Charles Deluvio on Unsplash

ACT Fibernet | IIM Lucknow | Interested in the trifecta of business, technology, and strategy.