File Connectivity

Connectivity

There are several ways to connect to TxB to begin sending or receiving files. Listed below are standard connectivity protocols we support. We may be able to support other connection protocols as well; please inquire if you’d like to discuss in more detail.

SFTP

Secure File Transfer Protocol (SFTP) is a protocol that allows for transporting files to a client SFTP server in a safe and secure manner.

Key Features:

• SFTP Push: You push payment files to our server
• SFTP Pull: You pull responses, reports, and statements from our SFTP server at an agreed upon cadence

Connectivity pre-requisites:

• SSH public key:
  • These are keys that will secure your data in transit. We will need to exchange public keys from both parties
  • SSH key types accepted: RSA with sizes 1024-4096
• IP Addresses or CIDR ranges
  • We will need to allow your IPs to pass through TxB firewalls
• PGP public key for Encryption and Signature
  • PGP keys help keep your data secure at rest. PGP keys are required to be used for both encryption and signing
    • PGP Encryption: PGP uses public/private key pairs. Encryption and signing requires the exchange of public keys by both parties. Encrypting a file requires the other party’s public key and is decrypted by them using their private key
    • PGP Signing: Signing a file is done using your private key and is verified by the other party using your public key
    • PGP key types accepted: DSA/ElGamal or RSA with sizes 1024-4096

SWIFT Services

SWIFT FIN

SWIFT FIN is used for sending stand-alone industry standard MT messages through the secure Swift network in store-and-forward mode. User-to-user, user-to-SWIFT, and SWIFT-to-user messages are sent and received within the FIN service

Key Features:

• You send the message via SWIFT network to the TxB BIC, and SWIFT routes the message to TxB, and vice versa
• Protection of data is ensured through a built-in SWIFT network security and RMAs

Connectivity Pre-requisite from the client:

• BIC: Includes only the SWIFT-registered BIC of the user that initiated the file transfer

SWIFT FileACT

FileACT is a service that lets an institution (client/TxB) drop their files (almost any format) in an envelope and post it over the SWIFT network. The addresses on the post are the sending and receiving institutions’ BICs

Key Features:

• All TxB supported file formats are supported to be received/sent via FileACT. These include ISO, NACHA and BAI2 formats
• It is suitable for transferring large files – bulk payments, large volume of data
• TxB supports both store-and-forward and real-time delivery modes, and both generic and corporate services of SWIFT FileACT
• Protection of data is ensured through a built-in SWIFT network security and RMAs

Connectivity Pre-requisite from the client:

• BIC: Includes only the SWIFT-registered BIC of the user that initiated the file transfer
• Certificate: Swift registers and publishes the default DN in FileACT directory to identify the sender of the message

Example US:

< Requestor > cn=test,ou=fa,o=gscrus33,o=swift < / Requestor > < Responder > cn=test,ou=fa,o=xyzabc33,o=swift < / Responder >

Example GB:

< Requestor > cn=test,ou=fa,o=gsldgb2l,o=swift < / Requestor > < Responder > cn=test,ou=fa,o=xyzabc33,o=swift < / Responder >