This feature sends flags distinguishing cardholder initiated transactions (CIT) and merchant initiated transactions (MIT) within the <recurring_processing_model_ind> parameter of the following API calls:
- assign_acct_plan_m
- authorize_electronic_payment_m
- cancel_acct_plan_m
- collect_from_account_m
- create_acct_billing_group_m
- create_acct_complete_m
- create_order_m
- create_order_with_plan_m
- manage_pending_invoice_m
- replace_acct_plan_m
- settle_account_balance_m
- update_acct_billing_group_m
- update_acct_complete_m
- update_acct_plan_m
- update_acct_plan_multi_m
- update_payment_method_m
- validate_acct_fraud_scoring_m
The input values for the <recurring_processing_model_ind> are the following:
0: Cardholder-Initiated Transaction—Credentials on File: a credit card transaction initiated by the cardholder for a new order or a plan upgrade that uses a credit card that is currently stored in Aria. (Default)
1: Cardholder-Initiated Transaction—a credit card transaction initiated by the cardholder for a new account or creating an order that uses an alternate credit card that is not currently stored in Aria.
2: Merchant-Initiated Transaction—Standing Instruction – Recurring: a credit card transaction initiated by Aria’s clients for a recurring charge that uses a credit card that is currently stored in Aria.
3: Merchant-Initiated Transaction—Unscheduled Credentials on File: a credit card transaction initiated by Aria’s clients for a non-recurring charge (one-time order or plan upgrade) that uses a credit card that is currently stored in Aria.
The output field of this call is <proc_initial_auth_txn_id>.
Fraud Scoring and Level 2/Level 3 Payments Now Supported
The Stripe payment processor integration has been enhanced to support fraud scoring and Level 2/Level 3 payments. Since Stripe fraud scoring returns both “review” and “failure” statuses, Aria has introduced the following fraud scoring settings on the collection group and payment gateway screens: Send Fraud Scoring Request, Change Status on Fraud Scoring Failure, Status on Fraud Scoring Failure, Change Status on Fraud Scoring Review, and Status on Fraud Scoring Review. For Level 2/Level 3 payments, these data are sent for payment actions regardless of Level 2/Level 3 eligibility; Stripe will pass this information on to the card networks for eligible transactions.
Stripe also supports fraud scoring for 3DS-enabled merchants, which allows you to obtain an account holder's fraud score or fraud score assessment. This can be implemented through a Direct Post configuration or the validate_acct_fraud_scoring_m API.
Account Updater
The Stripe payment gateway now supports the Account Updater for Visa® and Mastercard® card brands. When enabled, the account updater automatically updates your account holders' card information if available. The new field Webhook Secret was introduced at the payment gateway and collection group level (Configuration > Payments > [Payment Gateways/Collection Groups]); this provides an extra layer of security for data verification and message authentication for webhook notifications received from Stripe.
This feature supports Stripe event notification for the below behind-the-scenes events in Aria and updates client billing records:
- payment_method.updated
- payment_method.automatically_updated
- payment_method.detached
The Webhook Secret appears as shown:
Clients must configure their merchant account to allow webhook notifications by setting the end point URL in the Stripe dashboard. The endpoint URL has the following values:
Field | Description |
Client Number (Required) | The Aria client number |
Group Number (Optional) |
If the client would like notifications for a specific collection group, they can specify the collection group number in the URL. Note: If a collection group is not specified, the payment gateway settings will be used as a default. |