Skip to content
Planned capability

Payments and wallet for travel teams

Define the payment workflow your launch will need. Provider integrations are on the roadmap.

This module is planned. Supplier coverage, integrations and launch requirements are agreed for each project.

What to review

  • 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

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.

Scope this requirement before building.

Cards, local methods, agent wallets and B2B credit.

How this module is designed

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.

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.

Good to know:This module is specified and architected but not yet built. Nothing on this page should be read as a capability you can use today; the timeline is agreed per partner.

Planned 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

Your next step

Discuss how this fits your project.

Share your goal, current systems and any supplier contracts. We’ll review product availability, integration needs and the work to scope.