Create Simulated Incoming ACH Transaction

Use the Create Simulated Incoming ACH Transaction endpoint to simulate an incoming ACH transaction in the CV environment. This endpoint creates a pending transaction, defined by the template name and template values passed in the request, and returns an ACH transaction ID.

For instructions on using this endpoint, see Simulating Incoming ACH Transactions.

🚧

Warning

Do not use this endpoint in Production.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Form Data
string
required

Web service username, as provided by Galileo.
Pattern: Max 50 characters
Example: "AbC123-9999"

string
required

Web service password, as provided by Galileo.
Pattern: Max 15 characters
Example: "4sb62fh6w4h7w34g"

integer
required

Galileo-issued provider identifier.
Pattern: Max 10 digits
Example: 9999

string
required

A unique provider-generated ID to identify this API call. A UUID is preferred.
Pattern: 60 characters or less
Example: "9845dk-39fdk3fj3-4483483478"

string
enum
required

Name of the template that determines which template values are required to simulate an incoming ACH transaction.
Pattern: "CreditsAndDebits" or "ManualReviewNameMatching"
Example: "CreditsAndDebits"

Allowed:
string
required

JSON array containing the required metadata. See Incoming ACH Simulation Payload Values for the fields to include.
Pattern: JSON string
Example: Refer to Example templateValues string.

Headers
string
enum
Defaults to json

Use this header instead of the standard accept header to specify the response format.

Allowed:
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Response

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/xml