Skip to content

Fraud Screening

The following section is only applicable for Merchants using a fraud screening service integrated with the Worldline payment services.

The fraud screening services will screen payment transactions prior to the payment authorization and return appropriate status:

  • PASSED
  • BLOCKED
  • NOT SCREENED
  • HOLD

All information about the fraud result is included in the FraudResult element structure within the TransactionResponse. Note that the FraudResult Code and Message fields includes more detailed information about why the payment transactions has been blocked, but should not be used for logical decisions on the client side as they may change over time.

Example of Transaction Response with Fraud Result

XML
<TransactionResponse>
    …
    <FraudResult>
        <Status>BLOCKED</Status>
        <Code>4038</Code>
        <Message>Credit card on blocked list</Message>
    </FraudResult>
    …
</TransactionResponse>

Fraud screening responses

Passed

When the fraud screening system considered the data provided and believes the order should continue the payment process, the Worldline will reply PASSED in the FraudResult Status field.

Example of TransactionResponse

XML
<TransactionResponse>
    <TransactionId>1148858</TransactionId>
    <TransactionState>Processed</TransactionState>
    <StatusCode>0</StatusCode>
    <Description>Transaction accepted</Description>
    <TransactionType>Debit</TransactionType>
    <PaymentMethodType>Card</PaymentMethodType>
    <PaymentMethodId>1001</PaymentMethodId>
    <PaymentMethodName>Visa</PaymentMethodName>
    <PaymentMethodCategory>Card</PaymentMethodCategory>
    <FraudResult>
        <Status>PASSED</Status>
        <Code>1000</Code>
        <Message>Success</Message>
    </FraudResult>
    …
</TransactionResponse>

Blocked

When Transaction Defender processed the order data and believes the order to be fraudulent, the payment will not be processed. Worldline’ systems will reply with StatusCode 39003 (Screen order blocked by TD) and BLOCKED in the FraudResult Status field.

The FraudResult Code and Message fields includes more detailed information about why the payment transactions has been blocked, but should not be used for logical decisions on the client side as they may change over time.

Example of TransactionResponse

XML
<TransactionResponse>
    <TransactionId>1148859</TransactionId>
    <TransactionState>Declined</TransactionState>
    <StatusCode>39003</StatusCode>
    <Description>Screen order blocked by TD</Description>
    <TransactionType>Debit</TransactionType>
    <FraudResult>
        <Status>BLOCKED</Status>
        <Code>4038</Code>
        <Message>Credit card on blocked list</Message>
    </FraudResult>
    …
</TransactionResponse>

Not Screened

When the Transaction Defender service is not available, Worldline will continue the payment process and reply with NOT SCREENED in the FraudResult Status field.

Example of TransactionResponse

XML
<TransactionResponse>
    <TransactionId>1148858</TransactionId>
    <TransactionState>Processed</TransactionState>
    <StatusCode>0</StatusCode>
    <Description>Transaction accepted</Description>
    <TransactionType>Debit</TransactionType>
    <PaymentMethodType>Card</PaymentMethodType>
    <PaymentMethodId>1001</PaymentMethodId>
    <PaymentMethodName>Visa</PaymentMethodName>
    <PaymentMethodCategory>Card</PaymentMethodCategory>
    <FraudResult>
        <Status>NOT SCREENED</Status>
        <Code></Code>
        <Message></Message>
    </FraudResult>
    …
</TransactionResponse>

Hold

Reserved for future use.

Back to top