BillValidation Response Endpoint

Biller server to Biller Protocol

Request: POST /BillValidationResponse

Request ParametersLE

The various parameters are explained below:

Parent Property/Element	Property/Element Name	Mandatory	Data Type	Description
[ROOT] (No parent property / element)	refId	M	String	Unique identification assigned by the initiating BBPOU to unambiguously identify the transaction which is passed on, unchanged, throughout the entire end-to-end chain, binding the Fetch and Payment messages
	errorCode	C	String	Carries the compliance code indicating the reason for a failed transaction – not required for a successful transaction
	errorDescription	C	String	Description of the compliance code – not required for a successful transaction
	status	M	String Min Length – 1, Max Length – 100	Status of given request
	additionalInfo	M	Array	Additional information parameters sent by the Biller supporting fetch is copied in the payment request.
	tenantId	M	String Fixed length - 4	OU ID of request originating BOU

Expected Acknowledgement Parameters

The various parameters are explained below:

Parent Property/Element	Property/Element Name	Mandatory	Data Type	Description
[ROOT] (No parent property / element)	reason	M	String Min Length – 1, Max Length – 100	Reason of the Status
	code	M	String Fixed Length 3	Response code for a request
	status	M	String Min Length – 1, Max Length – 100	Status of given request

Json Formatted ResponseExample

    
    {
    "refId":"String", "errorCode": "String", "errorDescription": "String", "status": "String", "additionalInfo": [
    {
    "name": "String",
    "value": "String"
    }
    ],
    "tenantId" : "String"
    }

Json Formatted Response Example

    {
    "reason":"String",
    "code":"Integer", "status":"String"
    }