Treasury infrastructure for travel

Stop losing $400K a year to settlement you can't see.

Friday afternoon. Your treasury analyst is reconstructing the week's airline settlements from a CSV, a PDF, and a spreadsheet. $200K sitting in transit since Tuesday. CredaFi fixes this.

Request a pilot →↓ See how it works
3–5 days
Settlement window
50–100 bps
FX spread absorbed
12–15 hrs/wk
Manual reconciliation
$22B
Airline payment costs

The problem

One commercial chain. Fragmented operations.

Today — fragmented
With CredaFi — canonical
1
Booking recorded in PMS/GDS
Financial context not captured, just a booking reference
2
Customer charged at point of sale
Card or bank transfer, no link to downstream settlement
3
Bilateral wire to airline
3–5 days through correspondent banking
3–5 day delay
4
Remittance arrives without context
Airline can’t auto-apply, manual matching required
50–100 bps FX loss
5
Refunds create new objects with broken lineage
No link back to original booking or obligation
6
Finance reconstructs the story at month-end
12–15 hrs/week of analyst time
$400K–$600K/yr lost
1
AI agent ingests your existing settlement files
No booking system changes. Drop a CSV, PDF, or structured feed
2
Settlement objects created and reviewed
Each binding: booking ref, obligation, FX state, remittance, lineage
3
Batch netted, fewer transactions, lower fees
Refund credits offset against payables before funding
4
Settlement routes through the optimal rail
The routing engine selects the best path: stablecoin infrastructure, card network, or traditional banking. Days to hours on supported corridors.
Hours, not days
5
Payment meaning travels with the payment
Airline receives context with the payment. Auto-application becomes possible.
6
ERP-ready accounting output generated from the record
Close the books from the settlement object. Not from fragments.
Month-end in minutes

The product

One record. Both sides see the same truth.

Settlement Object

Every field. One record. From booking to close.

booking_ref: "BA-LON-2490183"
supplier: "British Airways / BA"
obligation: GBP 148,240.00
refund_credit: GBP 12,090.00
net_payable: GBP 136,150.00
fx_path: GBP → USDC → EUR
routing: OPTIMAL | stablecoin > card > wire
rail: "OpenFX"
state: "DELIVERED"
settlement_t: 4h 12m
erp_output: READY

Like CitiDirect for the new payment rails. The settlement object carries your settlement intent through whichever rail is optimal.

What it captures

Booking referencesObligation & net payableFX path & rateRemittance payloadRefund lineageSettlement stateTiming rulesException logERP outputFull audit trail

How it works

Six steps. No booking system changes.

01 — INGEST
AI agent reads your files
Drop a CSV, PDF, or feed. No booking system changes.
02 — REVIEW
Treasury team confirms
Human in the loop. Trust built one batch at a time.
03 — NET
Batch netting applied
Refunds offset payables. Fewer transactions, lower fees.
04 — FUND
Optimal rail executes
Routing engine picks the best rail per corridor. You never touch the infrastructure.
↓ Days become hours
05 — REMIT
Meaning travels with the money
Airline receives context with the payment. Auto-application becomes possible.
06 — CLOSE
ERP-ready output
Close the books from the canonical record, not from fragments.
↓ Month-end in minutes

Routing intelligence

One object. Three rails. The engine picks the best one.

Stablecoin Infrastructure
Card Networks
Traditional Banking
PartnersOpenFX, Bridge, UbyxPartnersVisa + Bridge, MastercardPartnersCorrespondent banking, local transfers
SpeedHoursSpeed1–2 daysSpeed3–5 days
CostLowest on supported corridorsCostCommoditizingCostHighest on cross-border
Best forCross-border corridors where speed and cost outperform correspondent banking. Fastest path: hours, not days.Best forCorridors where stablecoin-linked card settlement is live. Widest supplier acceptance. Existing relationships preserved.Best forDomestic settlement. Corridors where existing bank relationships are sufficient. Fallback when other rails are unavailable.

As the rail landscape evolves, CredaFi gains routing options without rebuilding the product. The complexity of choice is the product.

Why now

Three shifts converged. The window is open.

The rail layer is commoditizing
$150M+ raised in 30 days for horizontal stablecoin rails. Visa + Bridge expanding to 100+ countries. The intelligence layer above the rail is what doesn’t commoditize.
The old rails are contracting
Correspondent banking down 40% since 2011. $1.2B in airline funds trapped. Stablecoin volume hit $28T in Q1 2026, surpassing US ACH.
AI made integration tractable
LLM ingestion turns months of custom parsers into days of configuration. Every TMC format, one agent.
Nic Abel, Founder and CEO of CredaFi

Why CredaFi

Nic Abel

Founder & CEO, CredaFi

14 years at Citi building travel payment products across 31 EMEA markets. Head of Product for Commercial Card Payments. Ran the Citi relationships with HRG and CWT. Co-conceived Spring by Citi. I built the infrastructure on the other side of this problem. CredaFi is the product I couldn't build from inside a bank.

Citi — 14 yearsHRG & CWT relationships31 EMEA marketsSpring by Citi (co-conceived)SVB — embedded paymentsAmazon — B2B paymentsNon-BSP settlement designBS EE, Queen Mary LondonMBA, Warwick Business School

One corridor. One pilot.
Prove it works.

Phase 1 is deliberately narrow: one TMC, one airline, one corridor.
If you run non-BSP settlement and feel this pain, let's talk.

No pitch deck required. No commitment. Just a conversation about your settlement workflow.