Platform module
Payments and wallet
Cards, local methods, agent wallets and B2B credit.
Payment is where a travel platform meets regulation, and it is the area where we make the fewest claims until it is contracted and certified. The architecture is defined: card details never touch TravelCore infrastructure, tokenisation happens at a PCI-compliant provider, and the platform stores a token and a transaction record, never a pan.
For the markets TravelCore targets first, cards alone are not enough. The design assumes local rails, wallets and bank transfer alongside cards, and treats B2B credit as a first-class payment method with its own authorisation check at booking time.
This module is on the roadmap. It is not certified, not contracted with a provider, and not live.
The hard part
Refunds are not reversals
A travel refund is rarely the full amount: it is the payment minus the supplier's applied penalty minus non-refundable fees, sometimes across two currencies at two different FX rates. The refund record must reference the penalty the supplier actually charged, not the one that was quoted.
Capabilities
- Tokenised card payments through a PCI-compliant provider
- Local payment methods per market
- Agent wallets with deposits and real-time available balance
- B2B credit limits authorised at booking time
- Partial payments and payment schedules
- Refunds tied to the cancellation penalty actually applied
- Reconciliation against supplier invoices
Related
The rest of the core
Booking engine
One flow from search to voucher, for every product type.
Pricing and markup engine
Net rate to final price, by rule, versioned and auditable.
Hotel mapping and normalisation
The same property from many suppliers, resolved to one object.