Sample Payment Creation Request and Response in JSON Format
Using the below example, you can create a payment request for the 9663708377 account
Sample Payment Creation Request in XML Format
{
"C1-CreatePaymentService":
{
"accountNumberPayee": "SAV12544785",
"accountNumberTypeCdPayee": "C1_F_ANO",
"divisionCodePayee": "930",
"matchType": "SA-ID",
"matchTypeValue": "3583079049",
"statementId": "",
"currencyCd": "USD",
"paymentDt": "2019-03-04",
"sourceSystem": "",
"externalTransactionId": "",
"externalSourceId": "",
"tenderList":
[
{
"tenderType": "CASH",
"tenderCurrency": "USD",
"tenderAmount": 30,
"checkNumber": "",
"payorAccount": "9663708377",
"accountNumber": "",
"accountNumberTypeCd": "",
"divisionCode": "",
"micrId": "535343",
"externalReferenceId": "PQWERT",
"name": "",
"paymentTenderCharacteristic":
[
{
"characteristicType": "C1-TAUTH",
"characteristicValue": "123"
}
],
"paymentTenderCharacteristic":
[
{
"characteristicType": "C1-REFNM",
"characteristicValue": "45"
}
]
}
],
"tenderList":
[
{
"tenderType": "CHECK",
"tenderCurrency": "USD",
"tenderAmount": 400,
"checkNumber": "48112609",
"payorAccount": "9663708377",
"accountNumber": "",
"accountNumberTypeCd": "",
"divisionCode": "",
"micrId": "9292",
"externalReferenceId": "PQWERT",
"name": "",
"paymentTenderCharacteristic":
[
{
"characteristicType": "C1-TRVSE",
"characteristicValue": "ABC"
}
]
}
],
"paymentCharacteristic":
[
{
"characteristicType": "C1-REFNM",
"characteristicValue": "12"
}
],
"paymentCharacteristic":
[
{
"characteristicType": "C1RMPYMT",
"characteristicValue": "600"
}
]
}
}Sample Payment Creation Response in XML Format
{
"C1-CreatePaymentService":
{
"accountNumberPayee": "SAV12544785",
"accountNumberTypeCdPayee": "C1_F_ANO",
"divisionCodePayee": "930",
"matchType": "SA-ID",
"matchTypeValue": "3583079049",
"statementId": "",
"currencyCd": "USD",
"paymentDt": "2019-03-04",
"tenderList":
[
{
"tenderType": "CASH",
"tenderCurrency": "USD",
"tenderAmount": 30.00,
"checkNumber": "",
"payorAccount": "9663708377",
"micrId": "535343",
"externalReferenceId": "PQWERT",
"paymentTenderCharacteristic":
[
{
"characteristicType": "C1-TAUTH",
"characteristicValue": "123"
}
],
"paymentTenderCharacteristic":
[
{
"characteristicType": "C1-REFNM",
"characteristicValue": "45"
}
]
}
],
"tenderList":
[
{
"tenderType": "CHECK",
"tenderCurrency": "USD",
"tenderAmount": 400,
"checkNumber": "48112609",
"payorAccount": "9663708377",
"micrId": "9292",
"externalReferenceId": "PQWERT",
"paymentTenderCharacteristic":
[
{
"characteristicType": "C1-TRVSE",
"characteristicValue": "ABC"
}
]
}
],
"paymentCharacteristic":
[
{
"characteristicType": "C1-REFNM",
"characteristicValue": "12"
}
],
"paymentCharacteristic":
[
{
"characteristicType": "C1RMPYMT",
"characteristicValue": "600"
}
]
"paymentsDtls":
{
"paymentEventId": "966726526893",
"paymentId": "966611828652",
"messageValue": "SUCCESS",
"paymentStatusDesc": "Frozen",
"paymentStatus": "50"
}
}
}Note: We have given the above request and response samples to illustrate
how the attribute value pairs should be structured while sending a
payment creation 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 Creation Request and Response - Attribute/Value Pairs in JSON Format | Payment Creation Request and Response - Attribute/Value Pairs in JSON Format |