Create Simulated Incoming ACH Transaction

post

https://api-{corename}.{env}.gpsrv.com/intserv/4.0/createSimulatedAchTransaction

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.

Status codes

See Global Response Statuses for status codes that are common across endpoints.

Form Data

apiLogin

string

required

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

apiTransKey

string

required

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

providerId

integer

required

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

transactionId

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"

templateName

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:

templateValues

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

response-content-type

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

Status codes

default