APIs used for Integration

API name	Purpose
Model 1
Collect Payment API – PayU Hosted Checkout	Initiate first-time or repeat card payments on PayU Hosted Checkout with vault consent and `user_credentials` for saved cards.
Model 2
Model 2 – Zero Code Change for Vault Integration	Tokenize a card during the first `_payment` request with customer consent; PayU manages token creation and storage.
Get User Cards API	Retrieve a customer's tokenized cards for display at checkout.
Process Transaction with a Saved Card	Initiate a repeat payment using a stored PayU vault token.
Collect Payment API – Merchant Hosted Checkout	Submit merchant-hosted card payment requests with saved-card or token parameters.
Save a Card API	Create a card token after a successful payment (Model 3).
Model 3
Get User Cards API – Model 3	Retrieve saved card tokens created via Model 3 REST APIs.
Get Payment Details (Cryptogram) API	Fetch TAVV/cryptogram for a PayU or network token before initiating payment.
Edit a Tokenized Card API	Update a stored card token when the customer changes card details.
Delete a Tokenized Card API	Delete a stored card token for customer consent management.
General
Verify Payment API	Server-side reconciliation of transaction status after payment.

EXAMPLE QUESTIONS