Odin is the authorization service for the Dock platform that is used when processing transactions for issuers linked to it. The tool supports some of the top card brands in the world (such as Visa, Mastercard and ELO) and integrates with other ATM withdrawal services (such as TecBan and SaquePague).
One of the main differentiators in Odin is its customization functionality, as the rules available for the issuer are extensively customizable. Rules in Odin can be adapted over time, thus tailoring to different industry demands. That’s why the service experience might be quite different depending on the issuer.
The response time varies according to the rules that are set. For instance, in an external authorization, this response time increases if compared to an internal authorization when we have the entire flow within Dock because it needs the issuer’s external validation.
The protocol used in the external authorization might also impact on the response time, which is then arbitrary. The timeout set by the Dock platform for authorizations is measured in 3.000 milliseconds (or 3 seconds)—that is, the authorization always occurs in a time interval that is lower than that in order to ensure a streamlined, quick transaction.
We offer a lot of options for denying a transaction in order to increase security both for the issuer and the cardholder. See the following examples of reasons for denying transactions:
• Insufficient balance;
• Account status doesn’t allow it;
• Transaction amount;
• Operation set inappropriately or unset;
• Non-existent validation, such as a typo in the CVV number;
• In addition to other rules, on which your sales account manager can provide more details.
The issuer can set specific rules for denying e-commerce purchases using a physical card, which provides the transaction with more security by encouraging online purchases using a virtual card featuring a dynamic CVV. Another example of rule options for debit usage is limiting an amount for withdrawals, because it offers more security. So, the issuer and the cardholder are able to set a daily limit for operations in case the card is inappropriately used.
Also, for all validations for EMV as well as the ones specific for cryptogram and security, the Dock platform works with the newest chips in the industry.
Odin can be integrated with Falcon, a globally supported system used by Dock for providing issuers with security. The Dock authorizer can be fully integrated with the Jarvis module—a tool that enables the communication between both services. By using it, transactions can be sent to Falcon and, therefore, authorized or denied by security rules that are previously set and commonly used in fraud prevention systems.
Examples of fraud prevention rules which can be set on Falcon:
• Deny List by Establishment;
• Among others.
Updated 3 months ago