Sure, here is an explanatory postman documentation based on the given information: Authentication: [Admin-Integrator] Sign Up with Vesti Endpoint Description: This endpoint is used by admin-integrator to sign up with Vesti and generate Sandbox and Live Secret Key. This also helps to Onboard the Admin-Integrator. Request body format: { "AppId": "", "IntegratorDetails": { "Email": "", "Password": "" }, "SandboxSecretKey": "", "LiveSecretKey": "" } Example response: { "Status": "Success", "Message": "Admin-Integrator onboarding successful" } [User-Integrator] Sign Up with Vesti Endpoint Description: This endpoint is used by integrator's user to onboard with Vesti. Request body format: { "AppId": "", "IntegratorDetails": { "Email": "", "Password": "" }, "IntegratorType": "User" } Example response: { "Status": "Success", "Message": "Integrator onboarding successful" } [Admin-Integrator] Request New Secret Keys Endpoint Description: This endpoint is used by Admin-Integrator to Request for a New Secret Key. Admin-Integrator can provide the existing Sandbox and Live Secret Key, and a valid AppId to generate new Secret Keys. Request body format: { "AppId": "", "SandboxSecretKey": "", "LiveSecretKey": "", "integratorJWTAuthentication": "", "sandboxIntegratorJWTAuthentication": "" } Example response: { "Status": "Success", "Message": "New Secret Keys generated", "SandboxSecretKey": "", "LiveSecretKey": "", "integratorJWTAuthentication": "", "sandboxIntegratorJWTAuthentication": "" } [Integrator Details] Endpoint Description: This endpoint is used to fetch Integrator details by providing a valid Admin integrator credentials (email and password). Request body format: { "Email": "", "Password": "" } Example response: { "Status": "Success", "Message": "Integrator details fetched successfully", "AppId": "", "SandboxSecretKey": "", "LiveSecretKey": "", "IntegratorType": "Admin" } Checkout-Deposit Endpoint Endpoint Description: This endpoint is used to generate a payment link for Alumni's / Customers to make payments.