Additional Info for Cross-Border Payment APIs

Sample Response for UDF Update API

Success Scenario

  • If successfully updated
{
"status":"UDF values updated",
"transaction_id":"e5b8663df04581c085f9",
"udf1":"8000123",
"udf2":"4334343",
"udf3":"434343",
"udf4":"Abcd123",
"udf5":"INV000000004114"
}

Failure Scenarios

  • If the transaction ID is empty
( 
[status] => 0 
[msg] => Parameter missing 
) 
  • If the transaction ID is invalid
( 
[status] => 0 
[msg] => Invalid TXN ID 
) 

Sample Response for Invoice Upload API

Success Scenario

  • When a file is uploaded successfully: 
{
\"responseCode\":\"00\",
\"responseMsg\":\"File Uploaded Successfully\"
}

Failure Scenarios

  • When there is an error in uploading the file:
{ 
\“responseCode\”: \“103\”, 
\“responseMsg\”: \“Failed to Upload\” 
} 
  • When the file format is not supported:
{ 
\“responseCode\”: \“105\”, 
\“responseMsg\”: \“Not an OPGSP merchant, contact KAM\” 
} 
  • When the payuid is invalid:
{
\"responseCode\":\"107\",
\"responseMsg\":\"The PayuID in request is invalid\"
}
  • When a mandatory field is missing:
{
\"responseCode\":\"109\",
\"responseMsg\":\"All fields are mandatory, please check!\"
}