Block And Spam a Vpa
The api can be used to block or mark a collect request as spam.
application/json
This is a signature over combination of headers, payload. Refer Signature Calculation section for more details.
Will be shared while onboarding.
Will be shared while onboarding.
application/json
This is an epoch unix timestamp string. For example, 1496918882000. It can be used by us to invalidate older requests.
Merchant generated unique profile id for customer
Constraint: Alphanumeric string with dot(.). Maximum length is 256.
UPI request id of the collect request if requestType is TRANSACTION or mandateRequestId of the approve mandate request if requestType is MANDATE.
Constraint: 35 character alphanumeric
Vpa that has to be blocked/spammed
Denotes the request type for which block and spam vpa is triggered
Values: TRANSACTION | MANDATE
Boolean flag if the payee VPA has to be blocked
Boolean flag if the payee VPA has to be marked as spam
Stringified JSON for udf parameters
PSP status of the API
Values: SUCCESS | FAILURE
PSP response code for the API
PSP response message for the API
Unique id for the merchant as passed in request headers
Unique id for the merchant channel as passed in request headers
Merchant generated unique profile id for customer as passed in the request
Customer mobile number
Constraint: 12 digits mobile number string
Vpa that is blocked/spammed for the customer
Response status returned by gateway
Values: SUCCESS | FAILURE
Response code returned by the gateway for blocking/spamming the VPA
Response message returned by the gateway for blocking/spamming the VPA
Udf parameters as passed in the request
Have questions?
- Need help? Contact support
- LLM? Read llms.txt

