transmitTerminal
Overview
The transmitTerminal command manually initiates the transmission of transaction or terminal data to Shva, Israel's central clearing network. This command allows merchants to control their own transmission timing instead of relying on automatic daily transmissions.
Important: Merchants using manual transmission typically operate with automatic transmission disabled. When using manual transmission, you take full responsibility for managing all transmissions - the system will not automatically transmit transactions. You must ensure regular transmission to avoid delays in settlement and reporting.
Use cases
Manual settlement initiation: Trigger immediate transmission to Shva instead of waiting for the automatic daily cycle
Same-day reconciliation: Ensure transactions are transmitted for immediate settlement and reporting
End-of-day processing: Manually close the day's transactions before the automatic transmission
Urgent settlement requirements: Handle time-sensitive transactions that need immediate processing
Business workflow integration: Integrate manual transmission into specific business processes or schedules
Pre-weekend/holiday processing: Ensure transactions are transmitted before extended periods when automatic processing might be delayed
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 transmitTerminal 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
A successful transmitTerminal response contains transmission confirmation and details:
Key Response Fields:
result:000indicates successful transmission initiationtranId: Transaction ID for this operationtransmitId: Unique identifier for this transmission batchterminalNumber: The terminal that initiated the transmissiontransmitType: The type of transmission performed (e.g.,settlements)countTransmitted: Number of transactions transmitted (may be empty for immediate response)
Error response
Error responses include specific error codes and messages:
Code examples
Error codes
000
Permitted transaction (Success)
Transmission initiated successfully
500
TransmitId was not found
Verify the transmit ID and retry
502
Terminal is currently in transmit. Cannot make another transmit
Wait for current transmission to complete before retrying
503
Terminal cannot be retransmitted. There was no transmit failure
No retransmission needed - previous transmission was successful
504
Cannot transmit. There was a transmit failure. Please try to retransmit
Retry the transmission
534
Transmit exceeds allowed batches per transmit
Reduce the number of transactions or contact support to increase limit
550
Transmit service, error parsing GW request
Check request format and retry
556
Transmit service, error sending or creating request to BP
Communication error with processor - retry or contact support
558
Acquirer error - terminal does not exist
Contact System Administration - terminal configuration issue
Related commands
transmitInquire- Query transmission status and batch information after using transmitTerminaldoDeal- Process transactions that will later be transmittedRequest Structure - General API request format
Important: Manual transmission should be used judiciously as it affects the settlement cycle. Coordinate with your business processes to ensure proper timing and avoid conflicts with the automatic daily transmission.
Last updated
Was this helpful?