Cancel Simulated Incoming ACH Transaction

Cancel a simulated incoming ACH transaction that has not yet been processed. First, create a simulated incoming ACH transaction with the Create Simulated Incoming ACH Transaction endpoint, then use the ach_transaction_id in the response to cancel a transaction that has not yet been processed.

For instructions on using this endpoint, see Setup for Incoming ACH Simulation.

Form Data

ParameterReqData typeDescriptionPatternExample
apiLoginstringXProvider's web service username, as provided by Galileo for the requesting IP address.Max 50 characters"AbC123-9999"
apiTransKeystringXWeb service password, as provided by Galileo for the requesting IP address.Max 15 characters"4sb62fh6w4h7w34g"
providerIdint32XGalileo-issued unique provider identifier.Max 10 digits“9999”
transactionIdstringXA provider-generated ID that is unique to each API call. A UUID is preferred. Do not reuse this identifier for multiple API calls.60 characters or less"9845dk-39fdk3fj3-4483483478"
achTransactionIdint32XThe ach_transaction_id returned by the Create Simulated Incoming ACH Transaction endpoint is used.positive integer"354656"

RESPONSE
Output will be in similar format as mentioned in API Response above, except response_data:

status_code integer | null required
The response status code (may return a string for some statuses).

status string | null required
The condition of a process or response.

processing_time number | null required
The time elapsed in processing the transaction.

echo object | null required
A structure that contains transaction ID information.

	transaction_id string | null required
	An ID that represents an API transaction.

	provider_timestamp string | null required
	Store a related timestamp for reporting and troubleshooting purposes.

	provider_transaction_id string | null required
	Secondary transaction identifier (generated by a provider).

system_timestamp string | null required
A system generated timestamp.

rtoken string | null required
A Galileo-generated ID used for tracking.

Example request

curl --location --request POST 'https://api-exact.cv.gpsrv.com/intserv/4.0/cancelSimulatedAchTransaction' \
--header 'accept: application/json' \
--header 'content-type: application/x-www-form-urlencoded' \
--header 'response-content-type: json' \
--data-urlencode 'providerId=xxxx' \
--data-urlencode 'apiLogin=xxxxx' \
--data-urlencode 'apiTransKey=xxxxx’ \
--data-urlencode 'transactionId=353f909b-774d-49ff-b735-18337108ef2b' \
--data-urlencode 'achTransactionId=301'

Example response

{
    "status_code": 0,
    "status": "Success",
    "processing_time": 0.394,
    "response_data": {},
    "echo": {
        "provider_transaction_id": "",
        "provider_timestamp": null,
        "transaction_id": "353f909b-774d-49ff-b735-18337108ef2b"
    },
    "system_timestamp": "2023-05-17 10:44:53",
    "rtoken": "d7bf7c36-7da2-4770-a6f0-dbaf145de874"
}

See Global Response Statusesfor status codes that are common across endpoints.