Transmute · Legal
Exit & Termination Assistance Statement
Version 1.0 · Effective: July 14, 2026 · Last updated: July 14, 2026
403 Finance, Inc. ("403 Finance," "we," "us") provides Transmute (the "Service"), a hosted API for converting financial messages between SWIFT MT and ISO 20022 formats. This Statement explains what leaving the Service looks like. It is provided for information only; it is not a contract term and does not amend your agreement. It uses the defined terms of our Terms of Service — Service, Message Content, Output, Usage Metadata, and Customer.
1. Why Exit Is Simple
The Service is stateless by design, which removes the usual sources of exit friction. We hold no archive of your Message Content to migrate back to you, because message bodies are never persisted or logged. Output is returned to you in real time, at the moment of each request, so you already hold everything the Service produces. There is no data gravity and no lock-in: nothing accumulates on our side that you would need to extract in order to leave.
2. What You Can Take With You
(a) Usage Metadata. On request, we will provide an export of your Usage Metadata — the operational and metering records described in the Terms of Service (message type, size, duration, timestamps, status, warning counts, and billing counts). Email support@403fin.io to request one.
(b) Open standards in, open standards out. The Service reads and writes open, industry-standard formats — SWIFT MT, ISO 20022 MX, and JSON. There is no proprietary Transmute format to unwind: what you put in and what you get out are standard messages you can process with any conforming tool. Migrating away does not require converting out of anything proprietary.
3. Wind-Down Mechanics
(a) Credentials. On your request, and automatically on termination, your API Credentials are revoked (key revocation takes effect within about sixty seconds; outstanding OAuth tokens expire within fifteen minutes).
(b) In-flight work. Any batch jobs still in flight are purged on demand via DELETE /v1/jobs/{id}, and in any case self-expire within twenty-four hours. Idempotency-cache entries expire on their own within twenty-four hours.
(c) Account deletion. Because we do not yet offer a self-service deletion endpoint, account deletion is operator-assisted: email support@403fin.io and we will process it in accordance with our Privacy Policy and applicable law.
4. After Termination
Everything payload-bearing is already gone by the time you leave — in the ordinary course, within the twenty-four-hour windows above — because the Service keeps no historical Message Content or Output. Consistent with our Privacy Policy, we retain Usage Metadata and billing records for our own bookkeeping and statutory recordkeeping obligations for the applicable period. Nothing we retain contains message content.
5. Enterprise Transition Cooperation
For Enterprise customers, we will provide reasonable transition assistance on the terms set out in the applicable Enterprise agreement or order form. Those agreements govern the specifics; this Statement does not enlarge or replace them.
Change History
| Version | Date | Summary |
|---|---|---|
| 1.0 | July 14, 2026 | Initial release |