Skip to main content

BrightMatch Relay (SFTP)

As an alternative to the standard Relay webhook API, BrightMatch supports receiving loan application outcome data via SFTP. This is intended for lending partners who are unable to integrate with the Relay HTTP API directly.

Preferred method

The primary and preferred method for sending data back to BrightMatch is the Relay webhook API, which provides a standardised schema and real-time delivery. SFTP should only be used when a webhook integration is not feasible.

Overview​

Lenders can upload files containing BrightMatch loan application outcomes to a dedicated SFTP server. Ideally, files should follow the standard Relay schema as closely as possible, but we will accept any reasonable format and file type.

Connection Details​

Hostnamesftp.brightmatch.wemoney.com.au
Port22
UsernameYour lender name in lowercase (e.g. latitude)
PasswordShared separately upon request

To request SFTP credentials, contact your BrightMatch integration representative.

Connecting via CLI​

$ sftp latitude@sftp.brightmatch.wemoney.com.au

The authenticity of host 'sftp.brightmatch.wemoney.com.au (3.104.145.125)' can't be established.
RSA key fingerprint is SHA256:42fMTTE+4YDv0Om100yqyY2kjInhhhi+MuyxiO7aijk.
This host key is known by the following other names/addresses:
    ~/.ssh/known_hosts:29: s-1cc94f10232449ad9.server.transfer.ap-southeast-2.amazonaws.com
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'sftp.brightmatch.wemoney.com.au' (RSA) to the list of known hosts.
latitude@sftp.brightmatch.wemoney.com.au's password:
Connected to sftp.brightmatch.wemoney.com.au.

Once connected, upload your file(s) using the put command:

sftp> put outcomes-2026-03-19.csv
Uploading outcomes-2026-03-19.csv to /outcomes-2026-03-19.csv
outcomes-2026-03-19.csv                       100%   12KB  128.0KB/s   00:00

File Format​

Where possible, files should align with the standard Relay status update schema:

  • applicationId — the BrightMatch application UUID
  • status — one of Applied, Approved, Declined, or Withdrawn
  • declineReason — required when status is Declined
  • declineReasonDetail — free text providing additional context (required when status is Declined)
  • originalTimestamp — ISO 8601 timestamp of when the status change occurred

We accept CSV, JSON, Excel, or any other common data format. If your internal data format differs from the above, we will work with you to map your fields to the BrightMatch schema.