Skip to content

Contact

Ask for the thing you actually want to see.

One mailbox reaches us. Say which of these you are after — a demo on your own files, a technical question about a bank format or an ERP, or a partnership — and put enough in the first message that the reply can be specific instead of a calendar link.

The mailbox

How do I reach you?

The fastest way in is a demo on your own files. One click opens a pre-addressed email, already filled with the few things that make the first reply useful — edit it and send. We keep the address off the page, so the crawlers that harvest it never see it.

What to put in the first message

The shape of the group
Roughly how many legal entities, how many countries, how many banking relationships and which currencies you hold. That decides far more about the answer than the industry does.
What your banks and your ERP send
Which banks, and which ERP. If you already know the formats — MT940, CAMT.053, BAI2, CSB43 — say so. If you do not, name the banks and we will work it out from there.
What you are trying to see
A group position that traces back to a statement line. A close that stops depending on one spreadsheet. Both legs of every intercompany movement. Name the one that keeps costing you a day, and the demo gets built around it.

No form, no qualification questionnaire and no routing desk. There is one mailbox, and the reply comes from somebody who can open the file you are asking about.

Where we are

Where do we work, and where do letters go?

The company works in two places. Correspondence goes to the Madrid address, and a vulnerability report has a published route of its own.

Where we work

  • Austin, Texas
  • Madrid, Spain

Postal address

Calle Hermosilla, 48, 1º Dcha.28001 MadridSpain

Security reports

A vulnerability report goes through the published disclosure route rather than the general mailbox, so it lands in the right place immediately. The contact address and the policy are in the standard well-known file below, which is the first thing a researcher’s tooling checks. /.well-known/security.txt

The questions we get

What people ask before writing.

01Why is the address not printed on this page?
Because a raw address in a page’s HTML is free food for the crawlers that collect them. It is composed on the server and fetched when you click, so a person gets a mailbox and a scraper gets an empty page.
02Can you show it on our own files?
Yes. One entity, one bank statement and one ledger extract is enough for the first conversation to be about your figures rather than ours. Bring more and it covers more, but two files is the floor.
03Which file formats can you read?
MT940, CAMT.053, BAI2, CSB43 and ISO 20022 messaging among others, over the channels your banks support. The catalog is open: if one of your banks sends something the library does not read yet, we add it. The format library page lists what is there today.
04Where do I report a security issue?
Through the published disclosure route rather than the general mailbox. The contact address and the policy live in the standard well-known file named on this page, which is where a researcher’s tooling looks first and where a report reaches the right people fastest.
05Can we do all this in Spanish?
Yes. The product and this site are both in English and in Spanish, written natively in each rather than translated from one into the other, and so is the conversation.

Come with a question about one module.

A message that names the screen you want to see gets a demo built around that screen instead of a tour of everything.

One mailbox, one click above, and a reply from somebody who can open the file.