---
page_title: Integration Architecture
product: UPI TPAP SDK - HEADLESS
platform: Android
page_source: https://juspay.io/pe/docs/upi-tpap-headless-pe/android/overview/integration-architecture
llms_txt: https://juspay.io/pe/docs/llms.txt
product_llms_txt: https://juspay.io/pe/docs/upi-tpap-headless-pe/llms.txt
---


# Integration Architecture



![Image](https://dth95m2xtyv8v.cloudfront.net/tesseract/assets/upi-tpap-headless-pe/merch-inter-sdk.png)
*Integration Architecture*




###   Merchant Server Responsibilities


A merchant-operated server is required for this integration. It must securely generate JWS signatures and provide the signed payloads to the merchant app, receive and process callbacks, handle notifications of the app, and maintain merchant-owned customer records and transaction state. Keep the signing private key on the server; never expose it to the app.



---

## See Also

- [Pre-Requisites](https://juspay.io/pe/docs/upi-tpap-headless-pe/android/overview/pre-requisites)
