Sample Payment View Request and Response in JSON Format
Using the below example, you can view the payment history of the 8007760655 account.
Sample Payment View Request in JSON Format
{
"C1-ViewPaymentService":
{
"tenderType": "CHEC",
"accountIdentifierType": "C1_F_ANO",
"accountNumber": "SAV12544785",
"accountId": "8007760655",
"tenderType": "CHECK",
"division": "CB",
"sourceSystem": "ZZ_IWS_ES",
"c1ExternalTransactionId": "122",
"externalSourceId": "444",
}
}Sample Payment View Response in JSON Format
{
"C1-ViewPaymentService":
{
"getPayHistResponse":
{
"statusCd": "Success",
"payHistList":
[
{
"paymentEventId": "966818046432",
"paymentId": "966504142391",
"paymentDate": "2020-08-13",
"paymentAmount": "410.00",
"matchValue": "3583079049",
"currency": "USD",
"cancelReason": "ENTR",
"matchTypeDescription": "Contract ID match",
"paymentStatusDesc": "Canceled"
},
{
"paymentEventId": "966364498272",
"paymentId": "966635189345",
"paymentDate": "2020-08-13",
"paymentAmount": "400.00",
"matchValue": "3583079049",
"currency": "USD",
"cancelReason": "ENTR",
"matchTypeDescription": "Contract ID match",
"paymentStatusDesc": "Canceled"
},
{
"paymentEventId": "966584017975",
"paymentId": "966265993623",
"paymentDate": "2020-08-12",
"paymentAmount": "410.00",
"matchValue": "3583079049",
"currency": "USD",
"cancelReason": "ENTR",
"matchTypeDescription": "Contract ID match",
"paymentStatusDesc": "Canceled"
},
{
"paymentEventId": "966410695808",
"paymentId": "966550246069",
"paymentDate": "2020-08-06",
"paymentAmount": "37500.00",
"matchValue": "3583079049",
"currency": "USD",
"matchTypeDescription": "Contract ID match",
"paymentStatusDesc": "Frozen"
},
{
"paymentEventId": "966335717439",
"paymentId": "966824712954",
"paymentDate": "2020-08-06",
"paymentAmount": "37500.00",
"matchValue": "3583079049",
"currency": "USD",
"matchTypeDescription": "Contract ID match",
"paymentStatusDesc": "Frozen"
}
]
},
}
}Note: We have given the above request and response samples to illustrate
how the attribute value pairs should be structured while sending a
payment view request from the external system. However, you should
not seamlessly use this request sample in your environment because
the required pre-requisite data may not be available in your environment.
In such case, the system will give erroneous results.
Related Topics
| For more information on... | See... |
|---|---|
| Payment View Request and Response - Attribute/Value Pairs in JSON Format | Payment View Request and Response - Attribute/Value Pairs in JSON Format |