Cloud Tetra 1.35
Adding Serial Numbers In Responses
Added the injected serial number of the device on all response calls in PayGuardian Cloud Tetra
Exceptions Include:
Ping
Find Transactions
Example Response
{
"requestID": "*************************************",
"locationID": "*************************************",
"terminalID": "*************************************",
"approvedAmount": "11.13",
"authCode": "******",
"avsMessage": "Address not available (Address not verified)",
"avsResponse": "40",
"cardType": "Visa",
"cardClass": "Credit",
"cardModifier": "None",
"cardBin": "123456",
"expirationDate": "1231",
"extData": {
"receiptTagData": {
"maskedCard": "************0011",
"chipCardAID": "A0000000031010",
"atc": "592",
"invoice": "Tetra135-001",
"authCode": "******",
"entryMethod": "Contactless",
"totalAmount": "11.13",
"appLabel": "Visa"
},
"serviceFeeResult": {
"authorizationCode": "******",
"originalAmount": "700",
"gatewayTransID": "*******",
"gatewayMessage": "A01 - Approved",
"internalMessage": "Approved: 962224 (approval code)",
"gatewayResult": "00000"
}
},
"gatewayMessage": "A01 - Approved",
"gatewayResult": "00000",
"internalMessage": "Approved: 831953 (approval code)",
"isCommercialCard": "False",
"isoCountryCode": "840",
"isoRequestDate": "2025-07-21 09:13:54.203",
"isoTransactionDate": "2025-07-21 09:13:54.203",
"maskedAccountNumber": "************0011",
"merchantCategoryCode": "5999",
"merchantAccountCode": "*****001",
"networkMerchantId": "*****001",
"networkReferenceNumber": "******110",
"pnRefNum": "******305",
"remainingAmount": "0.00",
"resultCode": "00000",
"resultTxt": "Successful Request",
"serialNumber": "YOUR INJECTED SERIAL NUMBER HERE",
"submittedAmount": "11.13",
"timestamp": "20250721",
"token": "*************************************",
"transactionCode": "*************************************",
"transactionId": "*************************************"
}Adding Canceled and Timeout Screens
Created new screens for various device scenarios
If a transaction times out due to inactivity, the Timeout screen will appear.
If a transaction is stopped manually during the transaction process, the Canceled screen will appear.
Example Screen shots
Minor Enhancements / Fixes
Resolved an issue that allowed merchants to overwrite their device settings via an API call
Updated our responses to ensure signature bytes can be decoded to display an actual image if a signature is captured on a device.
Resolved an issue where webSocket connection was not reestablished until long after internet connectivity is restored on a device.
Resolved an issue where the Move/5000 would return a "Read Pin Failed" error on MSR debit swipe if no debit key is injected on the device.
Now returns a message to the user of “No Debit Key” in the API response and decline the transaction
Property of BridgePay Network Solution ©2026