Scope of work on the Merchant's side
To initiate the InPost Pay integration, the Merchant must perform implementation work described in the items below.
Merchant account configuration - enter store details according to the instructions and generate access details.
Authorization - implement authentication and authorization.
Widget frontend - implement the InPost Pay Widget.
Widget backend - issue endpoints described in Merchant Backend API, the purpose of which is to support functionalities in line with sequence diagrams.
Integration with InPost Pay (Basket App) - integration with API methods described in the InPost Pay (Basket App) section.
Testing the correct operation of the service in your store (InPost Pay - basic test scenarios).
Once technical deployment is completed, the integration is submitted for an audit using the contact form available in “For Business” and in the “Audit” tab. The service being submitted for an audit must be available only to tests at the dedicated link.
InPost Pay widget availability during implementation and tests
During implementation and testing of the InPost Pay service on the production store, the InPost Pay payment widget should be hidden for store customers. Widget visibility must be limited to testers and persons involved in the implementation process only.
Objective:
Hiding the widget prevents a situation where potential store customers could attempt to use an incomplete or inoperational InPost Pay service. In this way, we minimize the risk of negative user experiences and avoid problems related to incorrect operation of the payment function.
How it works:
Widget visibility must be controlled at the code or store configuration level. This may be achieved by implementing a widget access authorization mechanism that allows to display the widget only at the dedicated URL by calling it using an appropriate parameter, e.g.: https://shop.url?showInPostPay=true
Limited access: During testing, the InPost Pay widget is displayed only to specific users (e.g. by filtering based on IP address or test accounts).
Full widget activation occurs only once tests are completed, an audit is passed, the service is fully deployed and deemed ready for use by all store customers.