The Technology behind Araxatech's Nautilus

Technology

Our solution - Nautilus - is primarily driven by our belief that payment processor integration should not be embedded within the wallet. The wallet's purpose is to manage account balances and offer unique features distinguishing it from others, such as competitive FX rates and seamless remittance. Devoting 40-50% of its code to the complexities of a specific payment processor makes wallets challenging to maintain and restricts them to a single payment processor.

Integrating with a payment processor API for card creation and control (to create the card, obtain its PIN, and change its status) is a straightforward process usually accomplished within days. On the contrary, integrating into the transaction data feed poses a more complex challenge, often taking several months with numerous opportunities for failure.

Nautilus serves as our solution to this challenge. We provide fintech companies with quick, user-friendly, cost-effective, and comprehensive solution for seamlessly integrating into the transaction data feed. Notably, Nautilus ensures independence from the choice of payment processor, equipping fintechs with all the necessary tools for a smooth integration process.

Structured transaction data

We adopt a different approach from payment processors. Instead of putting all transaction data into a single structure, we create separate data structures for each unique transaction type. This approach offers several advantages:

• Simplified interface: Fields irrelevant to a specific transaction type are entirely excluded, ensuring the transaction only includes essential fields.
• Error Prevention: By including only relevant fields, the risk of errors due to inappropriate fields for the transaction type is eliminated.
• Structured Correspondence: The structure aligns with transaction types, eliminating the need for the wallet to decipher the received transaction type.

Delivery mechanism

Here, we again take a completely different approach to the payment processors. Instead of consolidating all transaction data into a single endpoint, we expect the wallet to have distinct endpoints based on the transaction type and the intended action. For example, a debit authorization can come as a request to authorize, or it can come as advice that has to be acknowledged – each of these transactions require different handling within the wallet.

Associate one card with multiple tokens

Nautilus' technology enables you to link one card within Nautilus to multiple payment processor tokens. This feature proves very useful when replacing a card for an individual (e.g., due to card expiration), migrating to a new payment processor, or enabling cardholders to use different cards from various payment processors globally. If one card is associated with multiple payment processor tokens, Nautilus seamlessly recognizes them as a single card and reports the same card usage to the wallet, without requiring the wallet to be aware of multiple linked cards.

Quick and easy integration

The consistent structure of transaction data combined with a clear data delivery method facilitates a fast and straight-forward integration. After completing this initial step and transitioning to testing and debugging, Nautilus offers a comprehensive transaction simulator and an environment for creating automated tests. Initiating card transactions in Nautilus on one screen while monitoring and debugging the wallet on another screen is a seamless process. Once a feature is complete, you can save simulated transactions as test cases for later use in regression testing.

Quick to results

Because transaction data is delivered using multiple specialized endpoints, as soon as an endpoint is implemented, all transactions of that type become fully supported. This allows developers to quickly achieve meaningful results.

Easy to maintain wallet

The structure of transaction data provided by Nautilus, coupled with the delivery mechanism that mandates implementors to split different operations into distinct endpoints, yields a more organized structure for the wallet. The wallet code becomes easier to understand and maintain once deployed in a live environment.

The independence of the transaction data feed from any payment processor also ensures a wallet free from payment processor-specific handling codes.

Quickly expand your wallet to new markets

Due to the independence of the transaction data interface from the payment processor, transitioning the wallet from one payment processor to another becomes seamless, facilitating its use across various territories.

Using multiple payment processors at the same time

Our technology supports using multiple payment processors as sources of data at the same time. It achieves this by either having some cards on one payment processor and some on the other or by having the same cards mapped to different physical cards residing on different payment processors.

Easy migration between payment processors

Because Nautilus' transaction data feed is independent of any payment processor, the wallet being developed using Nautilus is also free from dependency on any specific payment processor. This independence makes it easy to switch from one payment processor to another if needed. However, in the scenario where cards have already been issued with one payment processor and a transition to another is desired, migration may be necessary.

Nautilus simplifies this migration task by allowing the mapping of multiple card tokens belonging to different payment processors to the same card within its system. As a result, the wallet remains unaware of whether it is receiving transactions on card A issued by the first payment processor or on card B, which is issued as a replacement by the second payment processor. Using this feature enables a seamless payment processor migration without any downtime or service disruption for cardholders.