Get Money Movement Fraud

Use the Get Money Movement Fraud endpoint to perform ACH dual-party verification. This endpoint validates the owner of the account on the Galileo system and the external bank account owner.

Form Data
string
required

Identifier created by the Risk Squad. A fixed value for each client
Pattern: EPRP prefix followed by colon-separated identifiers
Example: EPRP:505:401:8385

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"

string
required

Galileo-issued provider identifier.
Pattern: Max 10-digit numeric string
Example: "9999"

string
required

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

const
enum
required

Event type.
Pattern: acct_vrfy
Example: acct_vrfy

Allowed:
const
enum

Event subtype.
Pattern: finicity
Example: finicity

Allowed:
string

Map trans_id to event_id
Pattern: One or more digits
Example: 2356109249

date-time
required

Map trans_ts to event_ts
Pattern: YYYY-MM-DD HH:MM:SS
Example: 2025-05-26 01:00:00

string
required

Partner ID
Pattern: One or more digits
Example: 505

string
required

Program ID
Pattern: One or more digits
Example: 9009

string
required

Product ID
Pattern: One or more digits
Example: 1234

string
required

Payment reference number (PRN)
Pattern: 12 digits
Example: 999101012345

string
required

Transaction XID
Pattern: One or more digits
Example: 1234

string
required

Balance ID
Pattern: One or more digits
Example: 4321

date-time
required

Application date
Pattern: YYYY-MM-DD HH:MM:SS
Example: 2025-04-18 00:00:00

boolean
required

Run GIVE.
Pattern: true or false
Example: TRUE

string

Counterparty PAN for AFT or OCT use cases
Pattern: 16 digits
Example: 1234567890123456

string

Counterparty bank account number
Pattern: 5–17 digits
Example: 841523654

string

Counterparty bank account type
Pattern: personal, business, or other
Example: personal

string

Counterparty bank account subtype
Pattern: checking or savings
Example: checking

string

Counterparty bank routing number
Pattern: 9 digits
Example: 021000021

number

Latest balance of the counterparty account
Pattern: Integer or decimal number
Example: 250.15

date-time

Timestamp when the balance of the counterparty account was pulled
Pattern: YYYY-MM-DD HH:MM:SS
Example: 2025-04-18 7:39:30

string

Counterparty bank account holder ID type: 'ssn', 'itin' or 'ein'
Pattern: ssn, itin, or ein
Example: ssn

string

Counterparty bank account holder SSN or tax ID
Pattern: 9 digits
Example: 123456789

string
required

Counterparty bank account holder first name
Pattern: Letter followed by letters, spaces, apostrophes, periods, or hyphens
Example: John

string

Counterparty bank account holder middle name
Pattern: Letter followed by letters, spaces, apostrophes, periods, or hyphens
Example: James

string
required

Counterparty bank account holder last name
Pattern: Letter followed by letters, spaces, apostrophes, periods, or hyphens
Example: Doe

string

Counterparty bank business name if the account type is business
Pattern: Non-empty text
Example: John Inc

string

Counterparty bank account holder date of birth
Pattern: One or more digits
Example: 29221

string

Counterparty bank account holder address line 1
Pattern: 1–60 characters
Example: 1417 N Rue St.

string

Counterparty bank account holder address line 2
Pattern: 1–60 characters
Example: APT 5520

string

City of the counterparty bank account holder
Pattern: Non-empty text
Example: Saint Charles

string

State of the counterparty bank account holder
Pattern: 2 uppercase letters
Example: MO

string

Zip or postal code of the counterparty bank account holder
Pattern: 5–20 characters
Example: 63301

string

2-letter country code of the counterparty bank account holder
Pattern: 2 uppercase letters (ISO 3166-1)
Example: US

string

Counterparty bank account holder billing address line 1
Pattern: 1–60 characters
Example: 1417 n. rue st.

string

Counterparty bank account holder billing address line 2
Pattern: 1–60 characters
Example: APT 5520

string

Billing city of the counterparty bank account holder
Pattern: Non-empty text
Example: saint charles

string

Billing state of the counterparty bank account holder
Pattern: 2 uppercase letters
Example: MO

string

Billing ZIP or postal code of the counterparty bank account holder
Pattern: 5–20 characters
Example: 63301

string

2-letter country code of the counterparty bank account holder
Pattern: 2 uppercase letters (ISO 3166-1)
Example: US

string

Counterparty bank account holder mobile phone number
Pattern: E.164 US format: +1 followed by 10 digits
Example: +11234567890

string

Counterparty bank account holder home phone number
Pattern: E.164 US format: +1 followed by 10 digits
Example: +11234567890

string

Counterparty bank account holder email address
Pattern: Email address
Example: [email protected]

string

Counterparty account holder IP address
Pattern: IPv4 address (four dot-separated number groups)
Example: 172.16.10.20

number
required

Counterparty name match score from Finicity
Pattern: 0–1 decimal
Example: 0.9

boolean

Counterparty phone number match indicator from Finicity
Pattern: true or false
Example: False

boolean

Counterparty ZIP code match indicator from Finicity
Pattern: true or false
Example: True

boolean

Counterparty email address match indicator from Finicity
Pattern: true or false
Example: True

string

Galileo PAN for AFT or OCT use cases
Pattern: 16 digits
Example: 1234567890123456

string

Galileo bank account number (PRN)
Pattern: 5–17 digits
Example: 999101523654

string

Galileo bank account type
Pattern: personal, business, or other
Example: personal

string

Galileo bank account subtype
Pattern: checking or savings
Example: checking

string

Galileo bank routing number
Pattern: 9 digits
Example: 210000221

number

Latest balance of the Galileo account
Pattern: Integer or decimal number
Example: 250.15

date-time

Timestamp when the balance of the Galileo account was pulled
Pattern: YYYY-MM-DD HH:MM:SS
Example: 2025-04-18 7:39:30

string

Galileo bank account holder ID type
Pattern: ssn, itin, or ein
Example: ssn

string

Galileo bank account holder SSN or tax ID
Pattern: 9 digits
Example: 123456789

string

Galileo bank account holder first name
Pattern: Letter followed by letters, spaces, apostrophes, periods, or hyphens
Example: John

string

Galileo bank account holder middle name
Pattern: Letter followed by letters, spaces, apostrophes, periods, or hyphens
Example: Arnold

string

Galileo bank account holder last name
Pattern: Letter followed by letters, spaces, apostrophes, periods, or hyphens
Example: Doe

string

Galileo bank business name if account type is business
Pattern: Non-empty text
Example: John Inc

string

Galileo bank account holder date of birth
Pattern: One or more digits
Example: 29221

string

Galileo bank account holder address line 1
Pattern: 1–60 characters
Example: 1417 N Rue St.

string

Galileo bank account holder address line 2
Pattern: 1–60 characters
Example: APT 5520

string

City of the Galileo bank account holder
Pattern: Non-empty text
Example: Saint Charles

string

State of the Galileo bank account holder
Pattern: 2 uppercase letters
Example: MO

string

Zip or postal code of the Galileo bank account holder
Pattern: 5–20 characters
Example: 63301

string

2-letter country code of the Galileo bank account holder
Pattern: 2 uppercase letters (ISO 3166-1)
Example: US

string

Galileo Billing address line 1 (AFT/OCT use cases)
Pattern: 1–60 characters
Example: 1417 n. rue st.

string

Galileo Billing address line 2 (AFT/OCT use cases)
Pattern: 1–60 characters
Example: APT 5520

string

Galileo Billing city (AFT/OCT use cases)
Pattern: Non-empty text
Example: saint charles

string

Galileo Billing state (AFT/OCT use cases)
Pattern: 2 uppercase letters
Example: MO

string

Galileo Billing ZIP (AFT/OCT use cases)
Pattern: 5–20 characters
Example: 63301

string

Galileo billing country code (AFT/OCT use cases)
Pattern: 2 uppercase letters (ISO 3166-1)
Example: US

string

Galileo Mobile phone number
Pattern: E.164 US format: +1 followed by 10 digits
Example: +11234567890

string

Galileo Home phone number
Pattern: E.164 US format: +1 followed by 10 digits
Example: +11234567890

string

Galileo account holder email address
Pattern: Email address
Example: [email protected]

string

Galileo IP address
Pattern: IPv4 address (four dot-separated number groups)
Example: 192.168.10.20

integer

Sequence number
Pattern: Integer, optional leading minus sign
Example: 20250500000000000000000000000000000

date-time

Map in_ts to request_ts
Pattern: YYYY-MM-DD HH:MM:SS
Example: 2025-05-27 13:46:37

date-time

Processing timestamp
Pattern: YYYY-MM-DD HH:MM:SS
Example: 2025-05-27 13:46:45

date-time

Effective date
Pattern: YYYY-MM-DD HH:MM:SS
Example: 2025-05-28 00:00:00

string

Original record
Pattern: Non-empty text
Example: ST

string

Batch header
Pattern: Non-empty text
Example: 5200Wyndham 134233889 WEBP2P 250528250528 1096001010000003

number

Transaction amount (map amt to trans_amt)
Pattern: Integer or decimal number
Example: 300.14

string

3-letter currency code
Pattern: 3 uppercase letters (ISO 4217)
Example: USD

string

Transaction code
Pattern: One or more digits
Example: 37

string

Transaction type
Pattern: Non-empty text
Example: AC

string

Status
Pattern: Non-empty text
Example: P

string

Status description
Pattern: Non-empty text
Example: Processed

string

Fee flag
Pattern: Any text, including empty
Example: true

number

Fee amount
Pattern: Integer or decimal number
Example: 1.50

string

Load type
Pattern: Non-empty text
Example: M

string

Original trace
Pattern: One or more digits
Example: 96001015089930

string

Return code dishonor
Pattern: Any text, including empty

string

Change code
Pattern: Any text, including empty

date-time

Change timestamp
Pattern: YYYY-MM-DD HH:MM:SS, or empty

string

Destination ID
Pattern: One or more digits
Example: 531

string

Destination institution name
Pattern: Non-empty text
Example: Sunrise_Bank_Wyndham_AC

string

Destination institution ID
Pattern: 9 digits
Example: 271081528

string

Destination account type
Pattern: Non-empty text
Example: S

string

Destination filename
Pattern: Non-empty text
Example: ACHs250527A531

string

Source ID
Pattern: One or more digits
Example: 531

string

Source institution name
Pattern: Non-empty text
Example: galileo:wyndham

string

Source institution category
Pattern: Non-empty text
Example: OTH

string

Source institution ID
Pattern: One or more digits
Example: 96001013

string

Source trace
Pattern: One or more digits
Example: 21000025074388

string

Source filename
Pattern: Non-empty text
Example: wyndham

string

Destination return filename
Pattern: Any text, including empty

date-time

Destination return timestamp
Pattern: YYYY-MM-DD HH:MM:SS
Example: 2025-03-07 10:20:28

string

Destination return trace
Pattern: Any text, including empty

string

Return code (required for certain event_subtypes)
Pattern: R followed by 2 digits
Example: R01

date-time

Return timestamp (required for certain event_subtypes)
Pattern: YYYY-MM-DD HH:MM:SS
Example: 2025-05-29 07:24:36

string

Source return filename
Pattern: Non-empty text
Example: ACH.366.250411.A

date-time

Source return timestamp
Pattern: YYYY-MM-DD HH:MM:SS
Example: 2025-04-11 11:45:50

string

Source return trace
Pattern: One or more digits
Example: 103113352137688

string

Original return trace
Pattern: One or more digits
Example: 125109013780198

date-time

Return settlement date
Pattern: YYYY-MM-DD HH:MM:SS
Example: 2025-01-17 00:00:00

string

Original return code
Pattern: One or more digits
Example: 01

string

Additional number
Pattern: One or more digits
Example: 0

string

Disbursement type
Pattern: One or more digits
Example: 0

integer

Retry count
Pattern: Integer, optional leading minus sign
Example: -1

date-time

Retry timestamp
Pattern: YYYY-MM-DD HH:MM:SS
Example: 2025-02-19 00:22:13

string

Batch category
Pattern: One or more digits
Example: 9009

string

Revision ID
Pattern: Any text, including empty

string

Same day indicator
Pattern: Y or N
Example: N

string

Original name
Pattern: Non-empty text
Example: HEALTH CARE SERV

string

Government origin indicator
Pattern: Y or N
Example: Y

string

Review flag
Pattern: Y or N
Example: Y

string

Review reason
Pattern: Non-empty text
Example: potential R17 return

string

Blocks ID used
Pattern: One or more digits
Example: 0

string

Identification number
Pattern: One or more digits
Example: 692101336968

date-time

Last enqueued timestamp
Pattern: YYYY-MM-DD HH:MM:SS
Example: 2025-06-02 03:28:33

string

Row insert origin
Pattern: Non-empty text
Example: aue1

string

Row update origin
Pattern: Non-empty text
Example: aue1

string

Description
Pattern: Non-empty text
Example: Bill Payment - Check

string

SEC code
Pattern: 3 uppercase letters
Example: WEB

string

Company name
Pattern: Non-empty text
Example: Nuttige LLC

string

OFAC status
Pattern: Any text, including empty

Response

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

© Galileo Financial Technologies, LLC 2026    Privacy Disclosure

All documentation, including but not limited to text, graphics, images, and any other content, are the exclusive property of Galileo Financial Technologies, LLC and are protected by copyright laws. These materials may not be reproduced, distributed, transmitted, displayed, or otherwise used without the prior written permission of Galileo Financial Technologies, LLC. Any unauthorized use or reproduction of these materials are expressly prohibited.