Changelog

News, additions, subtractions, and changes to the TxB platform.

Table of Contents:

• August 2024 (Executed)
• July 2024
• June 2024
• May 2024
• April 2024
• March 2024
• February 2024
• January 2024
• December 2023
• November 2023
• October 2023
• September 2023
• August 2023
• July 2023
• June 2023
• May 2023
• April 2023
• March 2023
• February 2023
• January 2023
• December 2022
• November 2022
• October 2022
• September 2022
• August 2022
• July 2022
• June 2022
• May 2022
• April 2022
• March 2022
• February 2022
• January 2022

August 2024 (Executed)

📂 File Interfaces 📂

• We now support the ability for clients to review and approve payment instructions sent via SFTP prior to Bank processing through the relevant payment rail

July 2024

📜 Balance & Transaction Reporting 📜

• We resolved several data consistency gaps in the Itemized and non-Itemized versions of our MT940, MT942, and BAI2 reports. ACH Company ID, ACH Company Entry Description, and Remittance info is now available for more transactions to aid client reconciliation

• We now support carriage return in Itemized BAI2 version.

June 2024

✅ User & Entity Management ✅

• We have made a breaking change to the v1 and v2 virtual account closure APIs. After the update, VIAs can only be closed if they have zero balance at the time of closure. As such, the remainingBalancePayment object will no longer be accepted. Instead, please use the v2 payouts API to reduce balance to 0 prior to submitting account closure requests

📜 Balance & Transaction Reporting 📜

• We enhanced the details available in our CAMT 052 & CAMT 053 reports by introducing the itemized version. Today, bulk payments like ACH are shown on your ledger as a single line item. The itemized CAMT 052 & CAMT 053 version can report the individual transaction level details inside a batch.

May 2024 (Executed)

📜 Balance & Transaction Reporting 📜

• We now support reporting up to 1000 transactions per file for MT940/942 subscribed via EBICS connectivity

April 2024

💥 Developer Portal 💥

• We now support self-service certificate management within the developer portal for API connectivity

📜 Balance & Transaction Reporting 📜

• We now support unstructured remittance in itemized MT940 under tag 86, which provides additional transaction information to the account owner

• We now support reporting up to 100 transactions for MT940/942 subscribed via EBICS connectivity

• We now support “PENDING” status in Pain.002 Payment status report for insufficient funds

March 2024

💥 Developer Portal 💥

• We have added a pain.008.001.08 ISO format guide for SEPA drawdown payments, along with a sample file.

📜 Balance & Transaction Reporting 📜

• We now support Carriage Return in Pain.002 file level acknowledgement reports.

February 2024

📜 Balance & Transaction Reporting 📜

• We now support multiple configurations of the same report type within a single delivery channel, introducing flexibility of reporting across accounts

January 2024

📂 File Interfaces 📂

• We now support sending MT942 via file transfer protocols

📜 Balance & Transaction Reporting 📜

• We now support the use of tag 86 which provides additional transaction information to the account owner on the itemized MT940 customer statement messages

December 2023

💸 Payments 💸

• We now have the ability to print bulk checks via V2 payments API
• We now have the ability to send CSV files for credit transfer and direct debit via SFTP 
• We now support ACH IAT payments via our V2 payments API

📂 File Interfaces 📂

• We now have the ability to send MT940 via file transfer protocols

November 2023

📜 Balance & Transaction Reporting 📜

• We now have a file based report for daily reconciliation of check deposit returns. This report contains details of returned checks and is available via file transfer protocols

October 2023

No new feature releases

September 2023

💸 Payments 💸

• We enhanced the payeeDocumentReference as an array in v1 and v2 payments API allowing clients to send multiple references of documents linked to a payment (eg. Invoice numbers)
• You can now initiate payments through v2 payments API and approve them using our client UI
• We have enabled our clients to identify the beneficiary as 'business' or 'consumer' in our v1 payment API

📜 Balance & Transaction Reporting 📜

• We added support for RTP outbound transactions on all files reports- BAI, CAMT.052, CAMT.053, MT940 , MT942 and the Transaction Report API

📂 File Interfaces 📂

• You can now send MT 101 messages with multiple creditors under one debtor
• You can now receive payment statuses for outbound RTP credit transfers via Pain002
• We enhanced the Pain002 files to include control totals for Check deposits 

August 2023

💸 Payments 💸

• We introduced the ability to make wire drawdown's from multiple debtor accounts via v1 and v2 collections API

✅ User & Entity Management ✅

• We have added a new mandatory section "Expected Monthly Activity" in both v1 and v2 entity APIs

📜 Balance & Transaction Reporting 📜

• You can now see a new field AddtlTxInf in the CAMT 52 Intraday report
• You now have the option of having itemized ACH debits within BAI reports
• You can now see a group header per account branch country in the EOD and intraday BAI reports

July 2023

💸 Payments 💸

• You can share the national identification number of the beneficiary through a new field “nationalIdentificationNumber” of v2 payments API
• You can share the account name of the account held at holder bank through a new field “accountName” of v2 payments API

📜 Balance & Transaction Reporting 📜

• You can now see “Company Discretionary Data” details on our BAI2 reports
• You can now see the updated text for “Transaction Description” as “Desc” under AddtlTxInf tag in the CAMT 53 EOD

June 2023

📜 Balance & Transaction Reporting 📜

Flexible Reporting

• You can now opt to include specific accounts to be reported on the Intraday/EoD reports across related entities
• You can now setup scheduled reports to deliver to CUI only
• You can now setup Human Readable NOC & Returns files to be delivered via File Transfer
• You can now receive a Pseudo NACHA file for inbound payments

📂 File Interfaces 📂

Payment Status Reporting

• Pain002 now supports reporting payment statuses for SEPA Credit Transfers

🔔 Webhooks 🔔

Incoming Webhooks

• You can now subscribe to Incoming Webhook for BACS, SEPA and SWIFT_ISO payments

May 2023

✅ User & Entity Management ✅

• You can now use 3 new v2 accounts APIs: Query account details, amend account details and close account

💸 Payments 💸

• You can now initiate BACS payments for UK via the v2 payment API

📜 Balance & Transaction Reporting 📜

• You can now see ‘Instruction for Next Agent’ on v2 transactions API for both inbound and outbound payments

April 2023

💸 Payments 💸

• You can now approve API initiated payments in our client user interface ("CUI")

📂 File Interfaces 📂

• You now have a new human readable (.txt) format for acknowledging receipt of payment initiation files to our customers. In addition to information within a payment status report (pain.002), this new format also contains control totals from the original payment files

March 2023

✅ User & Entity Management ✅

• You can now create entities and accounts in the Netherlands & Germany via API
• You can now create physical accounts via API

💸 Payments 💸

• You can now send bank to bank payments through our v2 payments API

📜 Balance & Transaction Reporting 📜

• You can now use the v2 documents API to download monthly, daily, and intraday account statements
• You now have a new file based report for daily reconciliation of check deposits. This report contains details of deposited, adjusted, and returned checks and is available via host to host delivery

February 2023

✅ User & Entity Management ✅

Entity Onboarding

• We have made operationDescription a required field in both entity APIs

💸 Payments 💸

ACH External Account

• You can now provide fundingPreferences (ACH, Wire) while initiating payments (domestic & cross-border) via External non-GS accounts using ACH

FX Rates

• We enhanced error response descriptions for our FX API suite,i.e.Query FX rates, Create an FX trade quote, Accept an FX trade quote, Get FX trade quote to enable faster troubleshooting for customers

📂 File Interfaces 📂

SEPA Payments via ISO XML 20022

• We added support that will allow for the initiation of SEPA payments credits via standard ISO XML 20022 formats (pain.001)

Multiple Payments via File

• You can now instruct multiple payments across branches and multiple rails (Domestic wires, cross border wires, cross currency wires, US ACH, BACS, Card) in one single ISO 20022 pain.001 file

📜 Balance & Transaction Reporting 📜

• We now support sending remittance advices in ANSI X12 EDI820 format for US-ACH
• We enhanced files reports- BAI, CAMT.052, CAMT.053, MT940 , MT942 and Transaction Reports API to provide appropriate transaction type codes for Tax Withholding transactions
• We added support for BACS Outbound Transactions on all files reports- BAI, CAMT.052, CAMT.053, MT940 , MT942 and the Transaction Reports API
• We streamlined reconciliation of drawdowns via the Transaction Reports API. The drawdown postings will now contain identifiers of the original drawdown request you sent to TxB
• We have added detailed transaction descriptions to CAMT.052 and CAMT.053 for all transaction types

January 2023

📂 File Interfaces 📂

BACS Payments via ISO XML 20022

• You can now send BACS payments credits via standard ISO XML 20022 formats (pain.001)
• After sending the payment files, you can also receive batch-level and/or payment-level status files (pain.002)

📜 Balance & Transaction Reporting 📜

• We enhanced reporting capabilities to support BACS Inbound Transactions on all files reports- BAI, CAMT.052, CAMT.053, MT940 , MT942 and the Transaction Reports API.

🔔 Webhooks 🔔

• We added ACH Return Reason Codes and descriptions on Webhooks

December 2022

💸 Payments 💸

Originate Collection API

• We introduced additional collection type (Wire) to our Originate Collection API (V2). You may continue to use our V1 Originate Collection API for current collection types

✅ User & Entity Management ✅

Entity Onboarding

• We introduced a new version of the entities API to support direct client onboarding

Documents

• We added a new version of the document API to support digital document transfer to and from TxB
• This would primarily be used for direct client onboarding (KYC docs) or ACH Dispute evidence

📜 ** Balance & Transaction Reporting** 📜

EDI Reporting

• We added support for sending remittance advices in ANSI X12 EDI820 format for Wires

November 2022

💸 Payments 💸

Originate Payments API

• We introduced the ability to fund payments (domestic & cross-border) via External non-GS accounts using ACH
• We have enabled our Financial Institution partners to initiate inter-Financial Institution (FI to FI) payments through our V2 Originate Payment API

Incoming Payments

• We enhanced the Notifications' API suite enabling clients to view and action on Check positive pay notifications
• These endpoints will now support positive pay for both ACH and Check payments

📜 Balance & Transaction Reporting 📜

SWIFT Reporting

• We added IBANs on our SWIFT MT900, MT910, MT940, MT942 and MT950 reports for Frankfurt and Amsterdam branches

📂 File Interfaces 📂

Payment Status Reporting

• We added support for original instruction ID in Payment Status Report (pain.002) Balance and Transaction Reports
• We added check numbers to BAI2 reports for check payments

October 2022

💸 Payments 💸

Originate Collection API

• We introduced a new version of Originate Collection API (V2) with new collection type (ACH IAT) and a better developer experience. You may continue to use our V1 Originate Collection API for current collection types

📂 File Interfaces 📂

Balance and Transaction Report

• We have enabled partners to subscribe to EoD and Intraday reports using API. This is supported on the following formats- BAI2, CAMT.052, and CAMT.053

September 2022

📜 Balance & Transaction Reporting 📜

SWIFT Reporting

• We enhanced the details available in our MT940 reports. Today, bulk payments like ACH are shown on your ledger as a single line item. We have enhanced the MT940 to optionally include individual payment level detail associated with ACH

SWIFT FileACT

• We now support delivery of SWIFT MT940, MT942, MT950, MT900, and MT910 messages via FileACT

📂 File Interfaces 📂

SWIFT FileACT

• We introduced the ability to accept SWIFT payment messages MT103, and MT101 over FileAct

August 2022

💸 Payments 💸

Originate Payment API

• We introduced a new version of our Originate Payment API (V2) with additional payment types (checks, cards & multi-party same currency payments) and a better developer experience. You may continue to use our V1 Originate Payment API for current payment types

📜 Balance & Transaction Reporting 📜

Ledger Reporting

• We introduced the ability to receive a single statement for multiple related entities. This is supported on the following formats – CAMT052, CAMT053, BAI, MT940, MT942, MT950. You can select the accounts (of multiple related entities), you want to receive your reports for, as per your preference

Status & Reporting

• We introduced the ability to report related party information for multi-party payments in Get Transaction Reports API and Query Payment Status API. This is supported on the following formats- CAMT.052, CAMT.053
• We enhanced our MT900 and MT910 to receive advice at virtual and linked physical account level

🔔 Webhooks 🔔

Payment Status

• We enabled webhook support for Fedwire drawdown payments

📂 File Interfaces 📂

Multi-party payments

• We added reporting of related parties information for multi-party payments. This is supported on the following formats – CAMT.052, CAMT.053, and Pain.002

EBICS

• We enabled the ability to connect with TxB using the EBICS protocol for payments and reporting

July 2022

💸 Payments 💸

Originate Payment

• We introduced the ability to include preferred rail (ACH, SWIFT, FEDWIRE) in the Originate Payment API

Documentation

• We added public documentation for NACHA file instructions as well as ISO Payment Instruction Guides and ISO Payment Status Guides

💰 Deposit Accounts 💰

EU Open Banking

• We introduced EU open banking APIs to enable EU TPPs to access GSBE accounts using our Open Banking APIs
• We enabled support for Payment Initiation Services (PIS) and Account Information Services (AIS)

📜 Balance & Transaction Reporting 📜

Balance Reporting

• We introduced a new API getRealTimeBalances to our suite that enables you to query ledger and available balances in near real-time

🔔 Webhooks 🔔

Incoming Payments

• We added webhook notifications for incoming payments across all rails
• We made webhook subscriptions more flexible. Clients can now opt to exclude specific payment rails from their webhook subscription

June 2022

💸 Payments 💸

Fedwire Drawdown

• We introduced the ability to send Fedwire drawdown requests via our Originate Collection API and track their status via our Query Payment Status API

💰 Deposit Accounts 💰

Product List

• We added pagination using limit and offset in our Get Product List API
• We have set default limit to 50 records, max records per request to 100, and added "hasMore" to the response object

📜 Balance & Transaction Reporting 📜

ABA Numbers in Transaction API

• Your ABA routing numbers will now be available in the referenceDetails section on Get Transaction Reports API

📂 File Interfaces 📂

Available Balances, ABA Numbers and Return Codes

• We have added available balances on CAMT.052, CAMT.053, BAI, MT940 and MT950 reports
• Your ABA routing numbers will now be available on the (Acct) section of CAMT.052 and CAMT.053 reports
• We added ACH return codes on payment status pain.002 reports

Flexible Reporting

• We have added additional flexibility on Intraday and EoD statements
• You can now select the accounts you want to receive your reports for, as per your preference
• This is supported for all Intraday and EoD file formats

May 2022

✅ User & Entity Management ✅

NAICS Codes Update

• We updated the NAICS codes used to identify "Green Lane" entities

💸 Payments 💸

Payment Template Management

• We released a new set of APIs that allow you to create and view payment templates over API
• This capability allows you to create 'bank account tokens' and then reference those tokens later when you want to make payments

📜 Balance & Transaction Reporting 📜

SWIFT Reporting

• We enhanced our MT940 and MT942 reports to include an ACH receiver’s identification number

April 2022

💰 Deposit Accounts 💰

Multi-Currency Account

• UK clients can now create Multi-Currency Accounts via API

• Multi-Currency accounts enable you to have a single account number or IBAN that natively holds up to 21 currencies (GBP, EUR, CAD, JPY, CHF, SEK, HKD, SGD, ZAR, AUD, NZD, NOK, DKK, HUF, PLN, CZK, TRY, RON, ILS, MXN, USD)

Product List

• We introduced an new API version that allows you to retrieve a list of all accounts and products you have with TxB
• The response includes links to both accounts and transaction endpoints

🔔 Webhooks 🔔

Documentation

• We added public documentation to support our growing list of webhook beta users

📜 Balance & Transaction Reporting 📜

SWIFT Reporting

• We added Swift Payments & Reporting Guides as well

March 2022

✅ User & Entity Management ✅

UK Client Onboarding

• You can now perform client onboarding via API in the UK. We are also adding one new field, branchCountry, which is an optional input parameter that defaults to US
• We added new possible values for two fields governmentId.type and legalStructure to support ID types and legal structures relevant in the UK

Entity Maintenance for Amber Lane Users

• You can now change an entity's properties such that the entity becomes Amber lane
• After Amber/Red lane is triggered, then TxB performs our review process

💰 Deposit Accounts 💰

UK Virtual Account Management

• You can now create virtual accounts via API in the UK
• This change also introduces a new version of the reserved account API that includes sortCode and iban

💸 Payments 💸

API Payment Approval in Client Website

• You can now configure 2FA for payments made via API. When you send wire payments over API, you or someone in your organization must review and approve the payment before being released to the network
• The Payment object will also get a new status PENDING_APPROVAL
• This feature will be turned off by default and must be opted into

📜 Balance & Transaction Reporting 📜

Ledger Posting ID Completeness

• Now, all TxB Initiated transactions (like interest and fees) will have a unique ID on reporting interfaces (e.g., MT940, TransactionReport API, camt, BAI, etc.)
• This feature makes it easier to reconcile transactions and manage duplicates
• The following fields will be non-null for TxB-initiated transactions: Transaction Report API - paymentEndToEndID and gsUniquePaymentId. camt - AcctSvcrRef, EndToEndId, and TxId tags. BAI2 - Bank reference number and Customer reference number will be available on record 16. MT940/942/950 - Reference of account owner and Bank reference will be available in tag 61. MT900/910 - Related reference will be available on tag 21

📂 File Interfaces 📂

ACH Payments via ISO XML 20022

• You can send ACH payments credits and debits via standard ISO XML 20022 formats (pain.001 and pain.008, respectively)
• After sending the payment files, you can also receive batch-level and/or payment-level status files (pain.002)

February 2022

✅ **User & Entity Management ** ✅

stateCode Validation Enhancement

• When onboarding a customer via API, we upgraded our state code validation addresses in the US & Canada
• If either US or CA is the country of the Address, the provided state code is now validated as per the ISO3166-2 standard

Added Data to Entity Object

• The following fields are now returned when getting the details of an entity: dateOfBirth, governmentId, doingBusinessAsName, websiteUrl, operationDescription and riskIndicators

💸 Payments 💸

Payment Notifications Robustness

• We added bug fixes and resiliency checks to ensure all incoming ach payments trigger a notification

📜 Balance & Transaction Reporting 📜

Payment Reversal in Transaction Report

• ACH Reversals will be more specifically identified with a new enum (AREV) in our Transaction Report API in the following field transactionTypeCode.subFamilyCode

Incoming International IAT Payments in Transaction Report

• When you receive an international ACH transaction (an inbound IAT), the full addenda information will now be available in messagesFromOriginator.remittanceInfo(link)

📂 File Interfaces 📂

Balance and Transaction Report Versioning

• We added a feature to make it easier for us to create new versions of standard reports
• This will make it easier for developers to integrate with new reports that have (potentially) breaking changes

Balance and Transaction Report Pagination

• We added pagination to ISO 20022 bank account management reports camt.052.001.02 and camt.053.001.02
• camt transactions will be sorted in reverse chronological order and new pages will be created for every 10,000 transactions
• Clients must opt-in to receive paginated reports

January 2022

💥 Announcement 💥

We made a new year's resolution to start a public change log. Yay!