All interfaces support 4k TPS as standard, circa 350 million transactions per day, but the Engine is capable of scaling seamlessly to meet your TPS requirements. SFTP offers a 12k TPS mode, meaning the Engine can enrich a billion transactions within 24 hours.

Interface	Use Case	TPS	Latency
API	Real-time	4k TPS as standard	<= 5 seconds for up to 4k transactions
Client-hosted Kafka	Real-time or batch	4k TPS as standard	<= 5 seconds for up to 4k transactions
Moneyhub-hosted Apache Kafka	Real-time or batch	4k TPS as standard	<= 5 seconds for up to 4k transactions
SFTP	Batch	4k TPS as standard 12k TPS for reduced latency	7 hours for 100 million transactions @ 4k TPS 2.5 hours for 100 million transactions @ 12k TPS (all figures exclude external network transfer to/from your estate)

Interface Considerations

API

The API is our recommended synchronous interface, especially when requiring request-response style communication.

🚧
If your peak TPS is above the advertised limit, or experience sustained throughputs that are consistently in the thousands of TPS we do not recommend this interface for your primary interface. In these cases the Apache Kafka or SFTP interfaces should be preferred. This is because it is difficult for the service to manage flow control & backpressure.

The API endpoints to facilitate this interface are detailed here.

Apache Kafka

We connect to your Kafka broker that hosts the topic to receive transactions from, and we write the enriched transactions to a topic on that broker. Alternatively, we offer an Apache Kafka service, enabling you to produce and consume messages on its topics.

Encryption through TLS and authentication via two-way TLS (mTLS) or SASL.

The schema for the messages is detailed here.

SFTP

We host an SFTP server where you can drop up to a billion transactions in an input directory, and we return the enriched results in an output directory.