Becknifying your application
Introduction
Becknify makes it easy for you to get your existing commerce application beckn enabled and onboard onto a beckn enabled networks.
How does it work?
For each network, you wish to participate , Becknify:
Provisions a subscriber url on your behalf to receive requests from the network.
Provisions a network access url for your application to make requests into the network.
Generates signing and encryption keys for your application to access the network.
Generates the subscription json, that may be shared with the registrar of the network while onboarding onto the network.
Stores and rotates your keys safely as mandated by the network policy.
Ensures incoming payloads carry valid signatures and comply with beckn api schema before sending an ACK response.
Ensures outgoing payloads are signed on your behalf and comply with beckn api schema.
Delivers the validated incoming payloads to your application’s endpoint that could be a webhook not returning any content, a message queue or a url that returns a synchronous response to the request from the network.
Supports Consolidation of callbacks from network participants and delivering them to you synchronously as response to your outgoing request.
As a seller’s platform
You need to:
Provide a base url or choose a queue to receive your /search, /init … requests
Validate becknify token to ensure requests are coming from becknify’s servers.
Process the payloads according to your business logic.
Return the reponse according to /on_search, /on_init … schemas or no content
If you return no content, you can later call an applicable call back url (/on_search, /on_init.. ) relative to the provisioned access point url to send your payload across to the bap..
As a buyer’s platform
You need to:
Provide a base url or choose queue to receive your on_search, on_select, on_init, on_confirm.. callbacks .
Return no content from url
Process the business logic async as needed
If you fire requests on the network via the access point , you can receive the responses synchronously or on your communication endpoint url or q