Braintree

Feature Levels

Braintree is a USA-based (Chicago, IL) payments company that primarily deals in mobile and web payment systems for e-commerce. Braintree provides businesses with the ability to accept online and in-app payments.

UI Configuration/Processing Options Tab

Aria now provides the following enhancements to its Smart Payments integration with the Braintree payment gateway:

With this release, Aria provides fraud feature support on the Payment Gateway and Collection Account Group levels (Configuration > Payments > Payment Gateways/Collection Groups) for pay methods 1 (Credit Card) and 13 (Tokenized Credit Card) for Visa and Mastercard.

As part of this enhancement, the following fields have been added to the Processing Options tab:

• Send Fraud Request—This field determines us to pass the fraud fields to Braintree as part of the “auth_fraud_score“ action via the validate_acct_fraud_scoring_m API (select Enabled from the drop-down list; more on API functionality is included on this page).
• Fraud Scoring Threshold Value—If the attempted transaction’s risk score value is “Greater Than Or Equal” to the configured threshold value and the fraud result is not Approve, then Aria treats the transaction as failure.
• Change Status on Fraud Failure—If this field is set to True and the transaction fails, then Aria will change the MPI status based on the New Status on Fraud Failure field.
• Send Level2/Level3 Data in the payment request (at the Level2/Level3 Data Options section)—select Yes to enable Level2/Level3 data (default is No).

► Level 2/Level 3 Data Considerations

Additionally, line items with a quantity of 0 will be filtered out when sending Level 2/Level 3 data to Braintree, as Braintree does not accept zero values at these fields.

Additional validations have been added for Level 2/ Level 3 data to Braintree.

Character limits have been added for the following string fields:

Field	Validation
name	Maximum 35 characters
unitOfMeasure	Maximum 12 characters
productCode	Maximum 12 characters
commodityCode	Maximum 12 characters

Decimal place limitations and other validations have been added for the following decimal values:

Field	Validation
quantity	4 decimal places, can't be zero or negative
unitAmount	4 decimal places, can't be zero or negative
totalAmount	2 decimal places
unit_tax_amount	2 decimal places, can't be negative
discount_amount	2 decimal places, can't be negative

Additional Level 3 fields have been added for sending Level 2/Level 3 data:

Field	Validation
shipping_amount	Setting at 0 for all payments cases as Aria does not support shipping amount
shipping_tax_amount	Setting at 0 for all payments cases as Aria does not support shipping amount
discount_amount	The total discount amount of line items
ships_from_postal_code	Maps to shipFrom_postalCode
shipping_postal_code
shipping_country_code_alpha3
tax_exempt	Set to False is product is taxable; otherwise, this is set to True

Note: When the tax_amount is $0, Aria will set tax_exempt to True because Braintree only processes products with a $0 unit_tax_amount and tax_exempt = True for Level 2/Level 3 processing.

The Advanced Options tab includes anti-fraud support, including the following fields:

• end_user_session_id , fraud_merchant_id and correlation_id—These fields are used to determine device data for fraud scoring.
• end_user_ip_address and end_user browser_agent—These fields are used to determine risk data for fraud scoring.
  • The customer ip address needs to be passed in the end_user_ip_address; we also allow account level override to be passed.
  • The customer browser needs to be passed in the end_user_browser_agent; we also allow account level override to be passed.
• fraud_merchant_id—This is often the same as the payment processor merchant ID.
• shipFrom_postalCode—This value must be set to True to enable sending this value as part of level 3 data during a payment action.

For determining device data, Braintree recommends client-side implementation to get the session id values and later pass those values in the API/UI to Aria to use the values at the time of fraud request.

The soft_descriptor tooltip at the Advanced Options tab has been modified to note that this field must be 30 characters or shorter for credit cards and 15 characters for ACH. It can only contain letters, numbers, spaces, and the special characters .* ,!'"()@/&#+$-

Support for soft descriptors (which note pending transactions after authorization by the issuing bank) has been added for pay methods 1 and 13. The soft descriptor can be provided using collection support APIs or via the soft_descriptor field at the Payment Gateway and Collection Group levels (Configuration > Payments > Payment Gateway/Collection Groups > Advanced Options). A maximum of 30 characters is allowed at the soft_descriptor field and can only contain letters, numbers, spaces, and the special characters (.* ,!''"()@/&#+$-).

As part of Braintree's Smart Payments Payment Gateway/Collection Group configurations, the Merchant Account Details tab (present in Braintree's legacy configuration from Configuration > Payments > Payment Gateways/Collection Groups > Merchant Account Details) has been added with the following fields:

• Merchant id—Unique identifier for Braintree's Gateway account.
• Private Key—Private key for Braintree's Gateway account.
• Public Key—Public key for Braintree's Gateway account.
• Merchant Account ID—This is an identifier for a merchant in Braintree's gateway that determines currency. If no Merchant Account ID is specified, the transaction will use the default merchant account.

The environment field at the Advanced Options tab has been added for the Payment Gateway and Collection Account Group levels. This value needs to be set to "sandbox" or "production" to perform a collection (recommended by Braintree). (note - see if pic needs to be updated - may need pic for Merchant Account Details also)

Supported Functionality