About Accertify
Accertify is a subsidiary of AMEX, which provides a rule based Fraud Prevention Engine, called Interceptas.
The service responsible for real time transaction scoring is called Real Time Decisioning (RTD), which receives the transaction request via HTTPs POST request and automatically scores the transactions based on rule set configured in the platform.
With Accertify’s Fraud Management solution, online merchants benefit from real-time decisioning through a sophisticated yet efficient fraud scoring engine that can screen transactions in milliseconds and turn large volumes of disparate data into actionable intelligence that reduces fraud.
In order to use the Accertify solution a contract is needed for the different Accertify services.
Logo |
|
Info | With Accertify’s Fraud Management solution, online merchants benefit from real-time decisioning through a sophisticated yet efficient fraud scoring engine that can screen transactions in milliseconds and turn large volumes of disparate data into actionable intelligence that reduces fraud. |
Type |
Interceptas
Accertify offers two types of transaction review model/workflow:
Optimal method: Both pre-authorization checks and post-authorization checks are performed
Alternative method: Either pre-authorization check or post-authorization check
For the integration all three possibilities are available:
Pre authorization only
Post authorization only
Preauth + Postauth
This Fraud Screening/Check on transaction can be used for several different payment methods, we focused on Credit Card and Paypal transactions but it can be extended.
Recommendation result of the Fraud Screening from Accertify is:
Accept – Transaction is considered non-fradulent
Reject – Transaction considered fradulent
Review – Manual review is required on Accertify´s backend by either Accertify or the merchant, purpose is an extra manual check and taking a final decision
Interceptas can deliver 2 types of responses, depending on which option is used:
Synchron response – with the options shown above
Asynchron response – in case of manual review (decision the either accepted or rejected)
Implementation
Computop has implemented the following components of Accertify:
Accertify Module used for Pre-authorization
Accertify Paytype used for Post-authorization
Accertify Module (Pre-auth)
The Accertify module implemented is the option to use a pre-authorization feature using our hosted payment page (payssl.aspx).
The practical way is that before doing an authorization, we can use the data sent by the merchant in the request and do a fraud check before the authorization takes place.
The logic that can be used is:
if the fraud check status is accepted = Computop triggers the authorization
if the fraud check status is reject, the authorization never takes place, customer can use a different payment method
if the fraud check is review – we can wait for the final decision or treat the attempt as an approval
Accertify Paytype (Post-auth)
The Accertify as paytype was implemented in order to be able to do fraud checks via server to server (accertify.aspx).
The customer doesn´t need to be at a place. The paytype option allows us to use the Accertify tool Interceptas independently from any other calls. Accertify can be accessed at any time.
These are some of the possible options:
PCNr (Pseudo Card Number – a tokenized card) for recurring transactions, using saved data of the customer,
changes in an existing transaction, change of address triggering an extra fraud check
possibility to risk check a customer without a transaction being done, account creation check
Special features
Accertify creates custom made URLs for each merchant account for both live and test environments
The possibility to use a "custom" parameter to include a number of agreed parameters between merchant/Accertify to aid on the fraud check but not relevant for the actual payment
if 3DS is used on a transaction, the relevant 3DS data in the response can also be sent to Accertify to be included in the fraud assessment
Support
This is fully depending on the type of payment used, at the moment we have this available for:
Credit Card
PayPal
Connectivity
Accertify will provide the following for each merchant using their services:
User
Password
Unique URL
Sequence Diagrams
Pre-Auth using HPP
Post-Auth
Paygate interface
Definitions
Data formats
Format | Description |
a | alphabetical |
as | alphabetical with special characters |
n | numeric |
an | alphanumeric |
ans | alphanumeric with special characters |
ns | numeric with special characters |
bool | boolean expression (true or false) |
3 | fixed length with 3 digits/characters |
..3 | variable length with maximum 3 digits/characters |
enum | enumeration of allowed values |
dttm | ISODateTime (YYYY-MM-DDThh:mm:ss) |
Abbreviations
Abbreviation | Description | Comment |
CND | condition | |
M | mandatory | If a parameter is mandatory, then it must be present |
O | optional | If a parameter is optional, then it can be present, but it is not required |
C | conditional | If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional |
Notice: Please note that the names of parameters can be returned in upper or lower case.
Calling the interface
Credit Card Request
Identical for both pre-authorization and post authorization fraud checks.
Important: In case of post-authorization fraud check, the acquirer response parameter are to be included in the request to interceptas.
To carry out a Accertify check via a Server-to-Server connection, please use the following URL:
https://www.computop-paygate.com/payssl.aspx
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.
The following table describes the encrypted payment request parameters:
| Key | Format | CND | Description |
|---|---|---|---|
PayID | an32 | M | ID assigned by Computop for the payment, needed in order to find the right transaction in case of asynchrounous responses |
TransID | an..20 | M | Merchant's Reference ID, main transaction identifier from merchant |
RefNr | an..20 | O | Merchant's Reference ID, second merchant identifier |
ans..30 | M | MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too. | |
IPAddr | ans..45 | M | Octets of numbers from 0-255 represented in decimal form instead of binary form. Example: 169.342.113.204. |
n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit). | |
a3 | M | Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table | |
bdStreet | ans..100 | M | Street name and street number in the billing address. Street and Nr are combined with a space character between and forwarded together. |
bdAddressAddition | ans..30 | M | Additional/complementary address line. Special character [;] is not allowed. |
bdCity | ans..40 | M | Town/city in the billing address |
bdState | ans..20 | M | Federal state in the billing address |
bdZip | ans..10 | M | Postal code in the billing address |
bdCountryCode | ans2 | M | Country code of billing address according to ISO-3166-1, alphanumeric 2 chars |
bdPhone | n..25 | O | Phone number in the billing address (only digits, no spaces and special characters) |
PayType | an..100 | M | Tells if Credit Card or PayPal order |
CreditCardHolder | ans..100 | M | Name of the card holder |
CCBrand | ans..50 | M | Card type: MasterCard, VISA, AMEX, DINERS, JCB or CBN. Please note the spelling! |
CCNr | n16 | M | Credit card number at least 12-digit, numerical without spaces |
CCExipry | numeric | M | Credit card expiry date (YYYYMM), e.g. 200507 |
MerchantCustom | JSON | M | Base 64 encoded JSON object is the format to be used |
Important: PayPal will be using the post-authorization Fraud check in the case below!
| Key | Format | CND | Description |
|---|---|---|---|
PayID | an32 | M | ID assigned by Computop for the payment, needed in order to find the right transaction in case of asynchrounous responses |
TransID | an..20 | M | Merchant's Reference ID, main transaction identifier from merchant |
RefNr | an..20 | O | Merchant's Reference ID, second merchant identifier |
ans..30 | M | MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too. | |
IPAddr | ans..45 | M | Octets of numbers from 0-255 represented in decimal form instead of binary form. Example: 169.342.113.204. |
n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit). | |
a3 | M | Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table | |
bdStreet | ans..100 | M | Street name and street number in the billing address. Street and Nr are combined with a space character between and forwarded together. |
bdAddressAddition | ans..30 | M | Additional/complementary address line. Special character [;] is not allowed. |
bdCity | ans..40 | M | Town/city in the billing address |
bdState | ans..20 | M | Federal state in the billing address |
bdZip | ans..10 | M | Postal code in the billing address |
bdCountryCode | ans2 | M | Country code of billing address according to ISO-3166-1, alphanumeric 2 chars |
bdPhone | n..25 | O | Phone number in the billing address (only digits, no spaces and special characters) |
PayType | an..100 | M | Tells if Credit Card or PayPal order |
paypalOrderId | C | Response parameter from PayPal – post auth fraud check only | |
BuyerEMail | ans..127 | M | PayPal email (with @ symbol) |
paypalAuthId | C | Response parameter from PayPal – post auth fraud check only | |
MerchantCustom | JSON | M | Base 64 encoded JSON object is the format to be used |
Synchronous response
| Key | Format | CND | Description |
|---|---|---|---|
TransID | an..20 | M | Merchant's Reference ID, main transaction identifier from merchant |
RefNr | an..20 | O | Merchant's Reference ID, second merchant identifier |
AccertifyReference | ans..4000 | M | |
AccertifyDescription | ans..4000 | M | |
ScoreWert | n..10 | M | |
Result | an..20 | M | Accertify – possible values ACCEPT, REJECT, REVIEW |
MerchantCustom | ans.. | M | Mirrored from the request |
AccertifyRemarks | ans..4000 | M | Base64 encoded XML |
Asynchronous response
| Key | Format | CND | Description |
|---|---|---|---|
TransID | an..20 | M | Merchant's Reference ID, main transaction identifier from merchant |
RefNr | an..20 | O | Merchant's Reference ID, second merchant identifier |
an32 | M | ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request. | |
AccertifyActionCode | an..3 | M | Accertify – Specifying who is taking the action – Values either PS or BCR |
Result | an..30 | M | Accertify – Release or Cancel |
TransactionDate | dttm..30 | M | |
AccertifyDetails | ans..4000 | M | Base64 encoded XML |