transmitInquire
Overview
The transmitInquire command retrieves metadata and status information about transmissions that have been sent to Shva, Israel's central clearing network. This command provides detailed information about transmission batches, including transmission time, number of transactions, success/failure status, and related identifiers.
This command is essential for merchants who need to track, audit, or troubleshoot their settlement transmissions, enabling comprehensive reconciliation and monitoring of the transmission process.
Use cases
Transmission status verification: Check if transmissions to Shva completed successfully or encountered errors
Reconciliation and auditing: Gather detailed transmission data for accounting and compliance purposes
Debugging transmission issues: Investigate failed or incomplete transmissions to identify problems
Settlement monitoring: Track when transactions were transmitted and processed by Shva
Batch analysis: Review transmission batches to understand settlement patterns and timing
Compliance reporting: Generate reports on transmission activities for regulatory requirements
Post-transmission validation: Verify transmission results after using
transmitTerminalcommand
Request structure
For a comprehensive overview of the API request format and authentication, see API Request & Response General Structure.
Send a standard Hyp API request to your assigned server endpoint with the transmitInquire command in the int_in parameter.
Server Endpoints: Use the server endpoint provided during merchant onboarding (e.g., https://your-hyp-environment-url/xpo/Relay).
XML payload structure
Required parameters
Optional parameters
Response structure
Successful response example
Key Response Fields:
result:000indicates successful inquirytransmitId: Unique identifier for this transmission batchtransmitStatus: Status of transmission (completed, failed, pending, etc.)startDateTime/endDateTime: When transmission started and endedtransmitStatistics: Detailed statistics including:shvaReferanceNo: Shva reference number for the transmissioncountTransmitted: Total number of transactions transmittedcurrencyTotal: Overall amounts and counts by debit/creditCard company breakdowns (isracard, visa, diners, amex, etc.)
Error response example
Key Error Fields:
result: Error code (500 in this example)message/userMessage: Description of the errortransmitInquire: Empty element when no data is found
Code examples
Error codes
000
Permitted transaction
Transmission inquiry completed successfully
308
An error occurred while executing a query in the database
Contact System Administration
444
Application Error
Contact System Administration
500
transmitId was not found
Verify the transmission ID exists and is valid
501
Terminal cannot be retransmitted
Call support for assistance
502
Terminal is currently in transmit
Wait for current transmission to complete before retrying
503
Terminal cannot be retransmitted
There was no transmit failure - retransmission not needed
504
Cannot transmit
There was a transmit failure - please try to retransmit
534
Transmit exceeds allowed batches per transmit
Contact System Administration
550
transmit service, error parsing GW request
Contact System Administration
552
transmit service, transmit_log not in status 0
Contact System Administration
553
transmit service, error getting transactions from DB
Contact System Administration
554
transmit service, error creating transactionData
Contact System Administration
555
transmit service, error creating 1402 messages
Contact System Administration
556
transmit service, error sending or creating request to BP
Contact System Administration
557
transmit service, error updating transmit log
Contact System Administration
558
Acquirer error - terminal does not exist
Contact System Administration
Related commands
transmitTerminal- Manually initiate transmissions (use transmitInquire to verify results)doDeal- Process transactions that are later transmittedRequest Structure - General API request format
Data Retention: Transmission records may have retention limits. For long-term reconciliation, consider extracting and storing transmission data in your own systems.
Last updated
Was this helpful?