Verification
During the processing of a normal Debit, Credit, or Prenote transaction the verification step will run any method of verifying a transaction that are turned on for the account. An Authorize call also runs these steps, but does not move money.
We currently support several Verification Methods:
Previous Payments (PrevPay)
Giact Account Checkings
Microbuilt Account Checking
Lexis Nexis Identity Checking
PrevPay (Previous Payments)
The Previous Payments Database is an internal repository that contains historical transaction data. It captures both positive and negative funding information and return records for future reference.
Giact Account Checking
Giact is a third-party verification partner that provides services to authenticate certain identity and banking information.
MicroBilt Account Checking
MicroBilt is a third-party verification partner that specializes in verifying certain identity and banking information.
Lexis Nexis Identity Checking
Lexis Nexis is a third-party verification partner that specializes in identity and consumer information.
These can be added to your account to run automatically with the transaction or authorization. You do not need to change your integration to support these, they happen during the processing of the transaction in realtime.
Every verification method will produce a scored model. All the scored model responses are added to the transaction to produce an overall transaction score. The transaction must reach the Goal Score to be Accepted/Processed. Every transaction starts at the Foundation Score. Often the Goal and Foundation is the same so that neutral responses will allow a transaction to process. This information is stored in the notes field.
Notes should not be parsed directly, you should rely on the Status/Message. We may change the notes without notice.
Example Notes ( this is not exhaustive and we may add features or notes in the future )
Text | Description |
|---|---|
PrevPay: 7 Funded +49 | Our Previous Payments Database has seen this account and routing number combination 7 times previously and they have produced funded transaction. We are scoring this positively. |
PrevPay: 4 Invalid -100 | Our Previous Payments Database has seen this account and routing number combination 4 times previously and they have returned for an Invalid type of return ( R02,R03,R03 ). We are scoring this negatively. |
PrevPay: 2 Invalid -100, 2 Closed Account +0 | Our Previous Payments Database has seen this account and routing number combination 4 times previously and they have returned for an Invalid type of return ( R02,R03,R03 ). We are scoring this negatively. |
PrevPay: nil +0 | The Previous Payments database has not seen this exactly account and routing number combination before. |
PrevPay+PM R: Match Return -10 | Previous Payments Pattern Matching verification has matched the transaction details to negative outcome previous transactions. This is a predictive measure, this is matching a pattern. |
PrevPay+PM F: Match Funding +10 | Previous Payments Pattern Matching verification has matched the transaction details to positive outcome previous transactions. This is a predictive measure, this is matching a pattern. |
MicroBilt Verbose Accepted. RiskLevel: L. Message: .: Microbilt Verbose Accepted Transaction +11 | We have verified the transaction information with MicroBilt, this transaction has been rated as a low risk of return. It is positively scored. |
MicroBilt Verbose Declined. RiskLevel: H. Message: NEG..1.0/10.78.: Microbilt Verbose Declined Transaction -25 | We have verified this transaction information with MicroBilt, there is negative information associated with the transaction and it has a high risk of return. This is negatively scored. |
Threshold exceeded: Single Transaction Amount Max | The merchant or Consumer thresholds are exceeded. The High Dollar Ticket amount is exceeded. |
Threshold exceeded: Transactions Daily Max | The merchant or Consumer thresholds are exceeded. The maximum number of transactions per day is exceeded. |
Threshold exceeded: Dollars Daily Max | The merchant or Consumer thresholds are exceeded. The maximum amount per day is exceeded. |
Customer: Information submitted failed customer authentication. -24 | For Giact the submitted consumer information has negative information. This is scored negatively. |
Account: Account Verified +25 | For Giact the account information has positive related information. This is scored positively. |
Customer: No Information +0 | For Giact the consumer has no information. This is scored neutrally. |
Customer: Customer authentication passed. +20 | For Giact the consumer has positive information. This is score positively. |
LexisNexis No check, insufficent data: : Authentication Pass - All entries left blank and not checked +0 | For Lexis Nexis there was not enough information passed in to check the identity of the consumer. This is neutrally scored. |
LexisNexis Invalid Address: : Address does not match -25 | For Lexis Nexis, the address does not match the recorded consumer information on file at Lexis Nexis. This is scored negatively. |
LexisNexis Phone Ok: : Phone match found +25 | For Lexis Nexis, the Phone information provided does match information on file at Lexis Nexis. This is scored positively. |
LexisNexis Address OK: : Address match found +25 | For Lexis Nexis the provided address does match information on file at Lexis Nexis. This is scored positively. |