Travel Ledger
  • Welcome to Travel Ledger Help
  • Registering on the Platform
    • Registering as a New Company
    • Two-Factor Authentication (2FA) Setup Guide
    • Registering as a User
    • Updating User Profile
  • Managing Transactions
    • Bookings Organisation and Management
    • Updating Bookings (Accept/Reject)
      • Updating Booking (Accept/Reject) Manually
      • Updating Booking (Accept/Reject) through Buyer Download & Upload File
      • Reviewing Completed Settlements and Remittance Advice
    • Duplication Checks
    • Reviewing Remittances
    • Payment History Page
    • Uploading Bookings
      • Upload Manually
      • Upload by Data Delivery Methods
        • FTP setup guide
      • Reviewing Data Delivery
    • File Formats for Upload
      • Extended File Format (Full Version)
      • Extend File Format (Lite Version)
    • Seller returns file (Rec)
    • Scheduling payments
  • Exporting Data & Reconciliation
    • Reconciliation Best Practice
    • Exporting Data from Grid Displays
    • Scheduling Reports in Task Scheduler
  • Notifications
    • Notifications Overview
    • Configuring Notifications
  • Managing your Partners
    • Company List
    • Invite Partners to the Platform
      • Sending Individual Partner Invites
      • Sending Bulk Partner Invites
    • Commercial Link Creation
      • Payments Overview
        • Payment Profiles
        • Business Terms
        • Settlement Schedules
    • Managing Commercial Links
  • TL Pay Account
    • Registration Process - Revolut Grow
    • Registration Process - Nium/Clearbank
      • UK Application (KYB/KYC)
      • EU Application (KYC/KYB)
      • Step-by-Step Guide: KYB/KYC Form Completion
    • Funding your TL Pay Account
    • Commercial Links required
    • Settling via your TL Pay Account
    • Viewing TL PAY Activity
    • Withdrawals
    • Suppliers not cutover to TL PAY
  • Billing
  • Managing your Companies and Users
    • Managing your Companies
    • Suspending and Archiving Head Office and Branches
    • User Creation
    • User Management
  • Processing Entity Schemes
    • Refunds on the ABTA Scheme
  • Help and Support
    • Public Holiday Schedules
    • FAQs
      • FAQs - General Platform Queries
      • FAQs - Registration and Initial Set Up
      • FAQs - Transactions Area
      • FAQs - Uploading Files
      • FAQs - Payments and Commercial Links
      • FAQs - Admin
    • Glossary of Terms
    • Glossary of Notifications
    • Testing with Travel Ledger
    • Release Notes
      • Release 1.26.0 (12/10/2023)
        • Release 1.26.1 (19/10/2023)
        • Release 1.26.2 (26/10/2023)
          • Release 1.26.3 (03/11/2023)
          • Release 1.26.4(18/11/2023)
      • Release 1.25.0 (31/08/2023)
      • Release 1.24.0 (27/07/2023)
      • Release 1.23.0 (06/07/2023)
      • Release 1.22.0 (28/06/2023)
      • Release 1.21.0 (08/06/2023)
      • Release 1.20.0 (25/05/2023)
      • Release 1.19.0 (11/05/2023)
      • Release 1.18.0 (13/04/2023)
      • Release 1.17.0 (23/03/2023)
      • Release 1.16.0 (09/03/2023)
      • Release 1.15.0 (23/02/2023)
      • Release 1.14.0 (09/02/2023)
      • Release 1.13.0 (16/11/2022)
      • Release 1.12.0 (07/09/2022)
      • Release 1.11.0 (25/07/2022)
      • Release 1.10.0 (02/05/2022)
      • Release 1.9.0 (17/03/2022)
      • Release 1.8.0 (02/03/2022)
      • Release 1.7.0 (27/01/2022)
      • Release 1.6.0 (09/12/2021)
      • Release 1.5.0 (29/10/2021)
      • Release 1.4.0 (07/10/2021)
      • Release 1.3.0 (04/10/2021)
      • Known Issues
    • Still Need Help?
Powered by GitBook
On this page

Was this helpful?

  1. Help and Support
  2. Release Notes

Release 1.17.0 (23/03/2023)

Guidance notes on the release 1.17.0

Improvements

Exponential Back-Off Applied to Password and 2 Factor Authentication

To enhance the security of the Travel Ledger platform, we have implemented an additional layer of password and 2 factor authentication security. This places a limit on the number of incorrect password/2FA attempts you can make before being locked out for increasing amounts of time. This protects the platform against brute force hacking attempts, maintaining the security of your access.

In order to accommodate genuine errors (typos, cap locks on etc), we allow users two “free attempts” where there will be no consequence for inputting the incorrect credentials . After allowing two un-restricted initial log in attempts, the third attempt will lock for 30 sec, fourth attempt 5 minutes and fifth attempt 30 minutes.

The fifth attempt will also trigger an email notification to your inbox, advising that numerous attempts have been made to access your account.

This change applies to both password and 2FA code input.

PreviousRelease 1.18.0 (13/04/2023)NextRelease 1.16.0 (09/03/2023)

Last updated 2 years ago

Was this helpful?