SECURE PAYMENTS

Travellin — Payment Security, Payment Processing, Fraud Prevention & Transaction Protection Policy

Last Updated: 24 August 2026
Effective Date: 24 August 2026

1. Purpose

This Secure Payments Policy explains how Travellin approaches payment security when customers purchase or reserve travel-related services through the Travellin Platform.

It covers:

• payment processing;
• payment security;
• card transactions;
• payment authentication;
• payment information;
• fraud prevention;
• payment-service providers;
• refunds;
• failed transactions;
• chargebacks;
• payment verification;
• and related security procedures.

Travellin is committed to using appropriate technical and organisational measures to protect payment transactions and customer information.

2. Travellin Platform

Company: BETZONE s.r.o.
Platform: Travellin
Jurisdiction of establishment: Czech Republic

General enquiries: info@travellin.info
Booking enquiries: bookings@travellin.info
Privacy enquiries: privacy@travellin.info
Telephone: +420 732 844 855

3. Secure Payment Processing

Where Travellin accepts online payments, payment transactions may be processed through authorised third-party payment service providers.

Depending on the transaction, Travellin may use payment infrastructure provided by:

• payment processors;
• acquiring banks;
• card networks;
• banking institutions;
• fraud-prevention providers;
• authentication providers;
• and other authorised payment-service providers.

The specific provider may vary depending on:

• country;
• currency;
• payment method;
• supplier;
• transaction type;
• and technical availability.

4. Payment Card Information

Where payment is processed through a third-party payment provider, Travellin generally does not need to receive or store the customer’s complete payment-card number.

Payment details may instead be transmitted directly to the authorised payment provider through a secure payment environment.

The payment provider may process:

• card number;
• expiry date;
• security information;
• cardholder information;
• billing information;
• transaction information;
• and authentication information

as necessary to process the transaction.

5. Card Security

Customers should enter payment information only through the legitimate Travellin booking/payment interface or the authorised payment environment to which Travellin directs them.

Customers should never send:

• full card numbers;
• CVV/CVC codes;
• banking passwords;
• one-time authentication codes;
• or other payment credentials

to Travellin by ordinary email.

6. Encryption

Travellin uses appropriate security measures intended to protect information transmitted through the Platform.

Secure transmission may use industry-standard encryption technologies such as TLS/HTTPS.

Customers should ensure that the address displayed in their browser corresponds to the legitimate Travellin website before entering sensitive information.

7. Payment Authentication

Depending on the card, issuing bank, country and transaction, the customer may be required to complete additional authentication.

This may include:

• confirmation through a banking application;
• one-time authentication;
• biometric authentication;
• password or PIN verification;
• or another authentication mechanism.

8. Strong Customer Authentication

European payment transactions may be subject to Strong Customer Authentication (SCA) requirements under applicable payment-services legislation.

Where SCA applies, customers may be required to authenticate a payment using two or more appropriate authentication factors.

The authentication process is generally controlled by the relevant payment provider, card issuer or bank.

9. 3-D Secure

Where supported, card transactions may use technologies such as:

3-D Secure / 3DS

to provide additional authentication and fraud protection.

The customer may be redirected to, or presented with, an authentication screen operated by their card issuer or payment provider.

10. Payment Verification

A transaction may be subject to automated verification.

Verification may consider:

• transaction amount;
• currency;
• payment method;
• booking information;
• device information;
• IP/network information;
• billing information;
• transaction history;
• authentication results;
• and fraud-risk indicators.

These measures are intended to protect customers and Travellin from fraudulent transactions.

11. Fraud Prevention

Travellin and its payment providers may use fraud-detection systems to identify suspicious transactions.

A transaction may be:

• approved;
• declined;
• temporarily held;
• subjected to additional authentication;
• or referred for further review.

12. Why a Payment May Be Declined

A payment may be declined because:

• the card issuer rejected it;
• insufficient funds are available;
• card information is incorrect;
• the card has expired;
• authentication failed;
• the transaction appears suspicious;
• the payment method is not supported;
• the supplier cannot accept the payment;
• or a technical problem occurred.

Travellin cannot necessarily determine the exact reason for a decline because the issuing bank or payment provider may not disclose detailed fraud-related information.

13. Travellin Does Not Guarantee Payment Approval

Successful submission of payment information does not necessarily mean that a transaction has been finally authorised.

A booking is considered paid only when the relevant payment and booking systems confirm the transaction according to the applicable booking process.

14. Payment Confirmation

Where payment is successfully completed, Travellin may provide:

• an on-screen confirmation;
• booking confirmation;
• payment confirmation;
• email confirmation;
• booking reference;
• or other transaction information.

Customers should retain their confirmation information.

15. Pending Payments

A transaction may temporarily appear as:

Pending

or may create a temporary card authorisation.

A pending transaction does not necessarily mean that Travellin has received the funds as a completed payment.

16. Card Authorisations

A bank or payment provider may place a temporary authorisation or hold on available funds.

This can occur before a transaction is finally completed.

The duration of an authorisation depends on the relevant:

• bank;
• card issuer;
• payment provider;
• transaction type;
• and applicable banking procedures.

17. Duplicate Charges

Travellin seeks to prevent duplicate transactions.

If a customer believes they have been charged twice for the same booking, they should contact:

bookings@travellin.info

with:

• booking reference;
• transaction date;
• amount;
• currency;
• and relevant payment information.

Customers should not send their complete card number or CVV/CVC.

18. Payment Errors

If a payment appears to have failed but funds appear to have been reserved or charged, the customer should not repeatedly submit the transaction without first checking the booking/payment status.

Repeated attempts can sometimes result in multiple temporary authorisations.

19. Payment and Booking Are Separate Events

A payment transaction and the final supplier booking confirmation may involve separate systems.

For example:

1. the customer submits payment;
2. the payment provider authorises the transaction;
3. Travellin receives payment status;
4. Travellin communicates with the relevant supplier or booking system;
5. the supplier confirms or rejects availability;
6. the booking is finalised.

The precise sequence can differ by product and supplier.

20. Payment Does Not Always Guarantee Availability

In certain technical circumstances, availability may change between:

• search;
• selection;
• payment;
• and final supplier confirmation.

If the requested service cannot ultimately be confirmed, the applicable refund process will apply.

21. Refunds

Refunds are processed according to the applicable:

• booking terms;
• supplier cancellation policy;
• Travellin refund policy;
• payment provider procedures;
• and mandatory consumer rights.

A refund may be returned to the original payment method unless applicable law or the relevant transaction circumstances require another method.

22. Refund Processing Time

The time required for a refund to appear in a customer’s account may depend upon:

• Travellin;
• the supplier;
• payment processor;
• acquiring bank;
• card network;
• and customer’s bank.

Consequently, a refund may be processed by Travellin before it becomes visible on the customer’s bank statement.

23. Currency Conversion

If the customer’s payment currency differs from the currency used by the supplier or payment provider, currency conversion may occur.

The applicable exchange rate may be determined by:

• Travellin;
• the supplier;
• the payment provider;
• card network;
• or customer’s bank.

Additional foreign-exchange fees may be imposed by the customer’s bank or card issuer.

24. Displayed Currency

The currency displayed during search or booking may not always be the currency in which the underlying supplier transaction is settled.

Customers should review the final payment screen before confirming the transaction.

25. Payment Fees

Depending on the payment method and applicable law, certain transaction-related fees may apply.

Any mandatory customer charge should be disclosed before payment is confirmed.

26. Payment Methods

Available payment methods may vary by:

• country;
• currency;
• supplier;
• booking type;
• transaction value;
• customer location;
• payment provider;
• and technical availability.

Examples may include:

• credit cards;
• debit cards;
• digital wallets;
• bank-based payment methods;
• and other supported electronic payment methods.

27. Payment Provider

The payment page may be operated technically by Travellin or by an authorised third-party payment service provider.

Where a third-party provider processes the payment, that provider may process payment data under its own contractual and privacy terms.

28. Payment Data and Privacy

Payment-related personal data is processed in accordance with applicable data-protection law and Travellin’s:

Privacy Policy

The categories of information processed may depend upon the payment method and transaction.

29. PCI DSS

Where card payments are processed through third-party payment infrastructure, the relevant payment provider may maintain security controls designed to comply with applicable payment-card-industry requirements, including the PCI DSS framework where applicable.

Travellin does not represent that every payment provider uses identical security controls.

30. Travellin Does Not Request Card Credentials by Email

Travellin will not ordinarily request customers to send:

• complete card numbers;
• CVV/CVC;
• online banking passwords;
• authentication codes;
• or similar confidential credentials

by ordinary email.

If someone asks you to provide these details by email claiming to represent Travellin, treat the request as potentially fraudulent.

31. Phishing Protection

Customers should be cautious of fraudulent messages pretending to be from:

• Travellin;
• a hotel;
• an airline;
• a travel supplier;
• a payment provider;
• or a bank.

A suspicious message may attempt to obtain:

• payment information;
• login credentials;
• authentication codes;
• identity information;
• or money.

32. Official Contact Channels

For general enquiries:

info@travellin.info

For booking and payment-related booking matters:

bookings@travellin.info

For privacy matters:

privacy@travellin.info

Telephone: +420 732 844 855

Customers should verify unexpected payment requests through official Travellin contact channels.

33. Payment Security Responsibility

Travellin maintains reasonable technical and organisational measures designed to protect its systems.

However, no internet transmission or electronic-storage system can be guaranteed to be completely secure.

Customers should also take reasonable steps to protect:

• passwords;
• devices;
• email accounts;
• payment cards;
• banking credentials;
• and authentication codes.

34. Customer Device Security

Customers should:

• keep their operating system updated;
• use an up-to-date browser;
• avoid entering payment details on suspicious websites;
• use secure networks where practical;
• protect their devices with appropriate security controls;
• and avoid sharing authentication codes.

35. Public Wi-Fi

Customers should exercise caution when entering payment information on unsecured public networks.

Travellin cannot guarantee the security of a network outside its own systems.

36. Account Security

If Travellin provides customer accounts, customers are responsible for maintaining appropriate security of their account credentials.

Customers should not share passwords with third parties.

37. Suspicious Transactions

If a customer believes that:

• their card has been used without authorisation;
• their account has been compromised;
• a payment was made fraudulently;
• or a booking was created without their authorisation,

they should immediately contact their bank/card issuer and notify Travellin where relevant.

38. Chargebacks

A customer should normally first contact Travellin concerning a genuine booking or payment dispute where appropriate.

However, nothing in this Policy prevents a customer from exercising rights available under:

• applicable law;
• their card agreement;
• payment-service rules;
• or applicable chargeback procedures.

39. Chargeback Investigations

If a chargeback is initiated, Travellin may provide the payment provider or financial institution with relevant transaction information necessary to investigate the dispute, subject to applicable law.

Such information may include:

• booking records;
• transaction records;
• payment status;
• confirmation records;
• cancellation information;
• refund records;
• and communications relevant to the dispute.

40. Fraudulent Chargebacks

Travellin may contest a chargeback where it has evidence that:

• the transaction was authorised;
• the service was provided;
• the customer received the booking;
• or the chargeback reason is inconsistent with the transaction.

This does not limit legitimate consumer rights.

41. Payment Security and Suppliers

Some transactions may involve a supplier’s own payment system.

For example, a supplier may process payment directly under its own booking terms.

Where this occurs, the supplier may be responsible for the relevant payment processing and security controls.

The customer should review the supplier’s applicable terms.

42. Payment to Travellin

Where Travellin itself collects payment for eligible services or extras, the transaction may be processed through Travellin’s authorised payment infrastructure.

The applicable checkout page should identify the relevant payment recipient where required.

43. Payment to Supplier

In some booking arrangements, payment may instead be made directly to the supplier.

The booking interface and applicable terms should identify the relevant payment arrangement.

Customers should not assume that every amount displayed on Travellin is necessarily collected by Travellin.

44. Third-Party Supplier Relationship

Travellin may act as a comparison, referral, intermediary or booking platform depending upon the particular transaction.

The entity responsible for:

• payment;
• booking;
• cancellation;
• refund;
• and fulfilment

may therefore differ between services.

The applicable booking documentation should be reviewed before payment.

45. Secure Checkout

Travellin aims to provide a checkout process designed to:

• minimise unnecessary exposure of payment information;
• use secure transmission;
• provide clear payment confirmation;
• reduce duplicate transactions;
• and detect suspicious activity.

46. Session Security

Travellin may use security measures designed to protect payment sessions against:

• unauthorised access;
• session manipulation;
• automated abuse;
• fraud;
• and other attacks.

Detailed security mechanisms are not publicly disclosed where doing so could weaken their effectiveness.

47. Fraud Detection Systems

Fraud-prevention systems may use automated analysis of transaction and technical information.

A legitimate transaction may occasionally be flagged incorrectly.

Where appropriate, additional verification may be requested.

48. Automated Decisions

Certain payment decisions may be made automatically by:

• payment providers;
• banks;
• card networks;
• fraud-prevention services;
• or Travellin’s technical systems.

Travellin may not control the decision of an external payment provider or card issuer.

49. Payment Security Does Not Guarantee Against Fraud

Travellin uses reasonable security measures, but no payment system can guarantee that:

• fraud will never occur;
• a third party will never attempt an attack;
• a supplier system will never be compromised;
• or a transaction will never fail.

Security controls are intended to reduce risk rather than eliminate it entirely.

50. Security Incidents

If Travellin becomes aware of a security incident affecting personal data or payment-related systems, Travellin will take appropriate steps required by applicable law.

This may include:

• investigation;
• containment;
• remediation;
• notification to competent authorities where required;
• and notification to affected individuals where legally required.

51. Data Minimisation

Travellin aims to collect and process only payment-related information that is reasonably necessary for:

• processing transactions;
• preventing fraud;
• maintaining booking records;
• resolving disputes;
• complying with legal obligations;
• and protecting the Platform.

52. Retention

Payment and transaction information may be retained for as long as reasonably necessary to:

• complete the booking;
• process refunds;
• handle complaints;
• resolve disputes;
• comply with accounting requirements;
• meet legal obligations;
• and protect legitimate interests.

Retention periods are governed by applicable law and Travellin’s Privacy Policy.

53. Payment Records

Travellin may retain transaction records including:

• transaction identifier;
• amount;
• currency;
• payment status;
• date/time;
• booking reference;
• supplier;
• refund status;
• and other information required for accounting or dispute resolution.

54. Security of Stored Information

Where Travellin stores payment-related information, it applies appropriate technical and organisational measures appropriate to the information and associated risks.

Sensitive card credentials should not be stored unnecessarily.

55. Third-Party Security

Where payment processing is outsourced, Travellin selects or works with providers appropriate to the relevant payment function and may rely on their security infrastructure.

Third-party providers may have their own:

• security policies;
• terms;
• privacy notices;
• compliance programmes;
• and technical controls.

56. Payment Provider Changes

Travellin may change payment providers or add additional payment methods to:

• improve availability;
• support new countries;
• support additional currencies;
• improve security;
• reduce transaction failures;
• or improve customer experience.

57. Payment Security and Accessibility

Travellin aims to ensure that payment interfaces are usable by customers with different accessibility needs, subject to the capabilities and limitations of integrated payment providers.

58. Children and Payments

Customers should not use Travellin to make payments on behalf of minors where the transaction is prohibited by applicable law or supplier terms.

Certain travel services may have age restrictions.

59. Payment Disputes

For a payment or booking dispute, contact:

bookings@travellin.info

Please provide:

• full name;
• booking reference;
• transaction date;
• amount;
• currency;
• payment method;
• and a description of the issue.

Do not send your complete card number, CVV/CVC or banking password.

60. Final Security Principle

Travellin’s payment-security principle is:

Protect payment information, minimise unnecessary exposure, use appropriate security controls, authenticate transactions where required, and provide customers with clear information about who processes and receives their payment.

Travellin cannot guarantee absolute security, but it will seek to maintain appropriate technical and organisational safeguards and to work with authorised payment providers to protect transactions.

Nothing in this Policy excludes any mandatory consumer, payment-service or data-protection right available under applicable law.

CONTACT DETAILS

BETZONE s.r.o. — Travellin
Maletín 9
789 01 Maletín
Czech Republic

IČO: 28802471
DIČ: CZ28802471

General enquiries: info@travellin.info
Booking enquiries: bookings@travellin.info
Privacy enquiries: privacy@travellin.info
Telephone: +420 732 844 855