Lightning track

Highly time-sensitive payment providers and payment gateways value quick response times in the region of 300-400ms. SEON's lightning track is designed to reduce transaction processing times to help Tier 1 payment processors achieve these results.

Note: Such gains are highly dependent on your integration type and optimization implementation.

Lightning track reduces the time it takes for SEON to return a response for analyzed transactions by 300-400 milliseconds.

Your total response time will depend on the type of queries you're running, the complexity of your rules, and your connection characteristics.

These gains are relative:

• If you run email address and phone number checks, this will account for the largest portion of your response times.
  • The 300–400 milliseconds time saving from using lightning track results in gains of 3.1 seconds to 2.7 (a 13% decrease).
• Complex velocity rules, especially those that compare large date ranges will result in extended Scoring Engine calculation times that lightning track will not influence.
• In use cases where you only need to run quick checks, e.g., an order placed by a familiar customer, you may see more relative gains.
  • E.g. Using IP data enrichment and simple velocity rules that compare the current transaction to others from the past hour or day, your response time can decrease from the range of 1.2s to below 1s (33% reduction in response time).

Did you know: If your integration relies heavily on digital platform and social media lookups, you can optimize your integration by only running these checks at different touchpoints. e.g. If data enrichment is run when you see a customer for the first time, SEON can store this data and correlate it to their future transactions. See our Integration Guide for more.

You can also adjust your data enrichment response times. Check the Finetuning Timeouts page to learn how.

Lightning track uses an async method to ensure that SEON provides transaction monitoring at a faster pace. The solution is best-utilized to prioritize speed and response times.

Lightning track will not change how your rules are calculated. However, it will result in eventual consistency, that is you may see slight differences in the results of certain velocity rules if lightning track is enabled.

Eventual consistency is a result of how the results of transaction analyses are returned to you before being saved to the SEON databases. 

Velocity rules calculate on the database of saved transactions. Thus, if you are sending us multiple transactions a second over your API integration, there will be a delay between when you receive transactions analysis results, and when those are reflected in velocity rule calculations for subsequent transactions.

Lightning track is an opt-in feature designed for customers who require faster response times because they handle a large amount of transactions.

Here’s how lightning track differs in a high load and high velocity e–commerce and payments scenario.

Lightning track gains are highly dependent on your integration and use case. Our team is happy to discuss its use with you during a consultation and scoping session with our technical Customer Success team. Reach out to our Customer Success team if you’d like to learn more.

Initial labeling

When on lightning track, you can also pair real-time transaction analysis with feedback, without using Label API. This allows you to train SEON’s machine learning at speed and ease.

Similarly to Labels sent via Label API, you can define your own labels by simply entering them in your API request. Use the initial_labels parameter as part of your Fraud API request when Lightning Track is enabled.
 

Get the most out of Lightning track and SEON by reading more about our Scoring Engine and tools.

Learn more:
Overview: Read about velocity rules and how to use them in the Scoring Engine overview.
Overview: Unlock the full power of SEON with our Machine Learning tools.
Guide: Understand Regular aggregates with our hands-on guide