Home > Aria Crescendo Documentation > Aria Crescendo core api > validate_acct_fraud_scoring_m Guide

validate_acct_fraud_scoring_m Guide

Table of contents
  1. Input Fields
  2. Output Fields
API Specification: validate_acct_fraud_scoring_m
Required Fields:
  • <client_no>
  • <auth_key>
  • <acct_no> or <client_acct_id> 
  • <amount>
  • <plan_instance_list> (array)
    • <plan_instance_list>
    • <plan_instance_no> or <client_plan_instance_id> 
  • <alt_pay_method> or <billing_group_no> or <client_billing_group_id> or <payment_method_no> or <client_payment_method_id>
Error Messages: validate_acct_fraud_scoring_m Error Messages

Additional Guidance:

Inputs passed to this API call will override any fraud options that you specified in your payment gateway, collection group, or Direct Post settings, unless stated otherwise below. 

You cannot obtain the fraud score for credit or debit cards enrolled in 3D Secure.

Input Fields

Field Name: Notes:
<amount>

To authorize a tokenized credit card:

  1. For the Braintree payment gateway, complete the required Aria configuration fields.
  2. For the Worldpay payment gateway, first add the client_acct_id to the account as described in the  Worldpay configuration notes.
  3. Do either of the following:
    1. If the token was already generated outside of Aria, set the <alt_pay_method> to 13 and pass in the <bill_agreement_id>; or
    2. If you need to generate a token for the card, set the <alt_pay_method> to 13 and pass in the credit card details.
  4. Pass in the <amount> to be authorized.
  5. Optionally pass a value into the <cc_id> field to identify the type of credit card you are authorizing.
  6. Optionally pass in a <recurring_processing_model_ind> to specify the kind of transaction you are completing.

You can use the <recurring_processing_model_ind> field only for payment methods for which  your payment gateway supports Cardholder Initiated Transaction​s (CIT) and Merchant Initiated Transactions (MIT).

Please contact your payment gateway representative for more information.

<plan_instance_no>

 A value at this field or <client_plan_instance_id> is required to honor the billing group's collection group for 3DS and non-3DS payment authorization.
<client_plan_instance_id> A value at this field or <plan_instance_no> is required to honor the billing group's collection group for 3DS and non-3DS payment authorization.
<billing_group_no> A value at this field or <client_billing_group_id> is required to honor the billing group's collection group for 3DS and non-3DS payment authorization.
<client_billing_group_id> A value at this field or <billing_group_no> is required to honor the billing group's collection group for 3DS and non-3DS payment authorization.

Output Fields

Field Name Notes
<recurring_processing_model_ind>

Currently, for only the Vantiv payment gateway, the value in this field will automatically be set to 2 if your payment gateway or collection group configuration has the Send orderSource as recurring for all transactions option enabled.

Refer to your payment gateway documentation to see if this applies.

Please contact your payment gateway representative for more information.

<proc_field_override> (array)

<transaction_type>

The value that you pass into this field will override the Recurring Options that you set in the Aria application under:

  • Configuration > Payments > Payment Gateways > Chase Paymentech/Vantiv > Gateway Options; and
  • Configuration > Payments > Collection Groups > Chase Paymentech/Vantiv > Collection Group Options.

Currently, only Chase Paymentech and Vantiv support this field. Other payment gateways might not honor all of the allowable values for this field. You will need to check your payment gateway documentation for confirmation.
 
Aria will use this order of precedence to determine the transaction type:

  1. value passed into this field
  2. collection group configuration
  3. payment gateway configuration
  4. transaction type that you specified in the <recurring_processing_model_ind> field 
<proc_3dsecure_data> Not all values for this field apply to all payment gateways. In addition, not all payment gateways support 3DS. The payment gateways documentation identifies payment gateways that support 3DS. Please contact your payment gateway representative for more information about which version of 3DS is supported and other details.
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
Powered by CXone Expert ®