Stripe

Payment Methods

Payment Terms

Authorization and Capture

Stripe supports two-step payments, also known as “authorization and capture.” This process allows you to authorize a charge and wait to settle it later.

• Authorization: Once the issuing bank (ie. the bank of the cardholder) has accepted the authorization, you have seven days to capture the payment. During this 7-day period, the payment is guaranteed by the issuing bank, so there’s no risk for a merchant to decline a payment that has been authorized over the past seven days.
• Capture: When you’re ready to actually accept the payment, you’ll just need to make a second API call to capture the charge. By default, we’ll capture the total amount that was authorized.

The following APIs support this feature:

• authorize_3dsecure_m
• authorize_electronic_payment_m
• update_payment_method_m

3DS 1.0 and 2.0 Authentication

To support the Stripe 3DS 2.0 flow, we have introduced a new option, "Payer Authentication Settings," in the Payment Gateway and Collection group UI screen.

3DS Termination URL – When using 3DS (1.0/2.0) in Aria, you must provide the Merchant Website URL at this field (for Payment Gateways and Collection Groups). This will be invoked when the shopper challenge is complete. Otherwise, the transaction will not be completed, and the Aria authentication API will return a validation error. For direct post, the value should be 'https://secure.<environment>.ariasystems.net/api/auth_3ds2_notification_receiver.php' (with the environment name specified by the client).

The Stripe 3DS authentication is a three-step process, as follows:

1. Execute the authorize_electronic_payment_m or update_payment_method_m api with credit card details, billing address details and <attempt_3d_secure> as 'true' to perform client authentication. The API will then return the <proc_payment_id> (as the outer level output field) and <redirect_issuer_url> (value in the <proc_3dsecure_data/proc_3dsecure_auth> data array) in the response.

2. Use the <redirect_issuer_url> directly in the browser and execute it. A challenge/redirect window pops up based on the 3ds 2.0 or 3ds 1.0 transaction details; submit the challenge/redirect form.
3. Execute the authorize_3dsecure_m API with the <proc_pymnt_id> from Step 1, perform the authorization and verify the API result to complete the 3ds authentication-based authorization.

The following APIs support this feature:

• authorize_3dsecure_m
• authorize_electronic_payment_m
• update_payment_method_m

Minimal Authorization and Automatic Authorization Reversal

1. Since Stripe currently only supports the tokenized credit card payment method (pay method = 13), Aria has introduced a processor-specific configuration Validate card on Token creation > Requires card validation in the UI for both payment gateways and collection account groups. If this configuration field is enabled, then Aria performs a minimal amount authorization when creating the token. The field appears below:

2. All credit cards are tokenized within Stripe. Therefore, Tokenized Credit Card (TCC) payment method is the supported payment we have implemented.  Aria only permits the validate_payment_information_m API to operate $1 auth/minimal amount on a pre-existing payment method record (<seq_no> input alone) for <pay_method_type> 13 in Stripe. Otherwise, an error message is generated when passing pay_method=13 with credit card details in the validate_payment_information_m API.

Stripe also supports reversing pre-authorizations on credit cards outside of $1. After performing the authorization, click on Accounts > search for the account > Payments & Credits (left panel) > Current Authorization Reversals tab > Create a New Auth Reversal. All pending authorizations that can be reversed display on this screen.

Tokenization

Stripe supports secure encryption for credit card and bank accounts. An encrypted reference to Personal Account Numbers called a payment method ID is created and used for transaction processing.

Refunds

Aria allows refunds on a previously captured Stripe transaction up to 180 days after its capture. The success or failure of a refund is returned in our API response.

Soft Descriptors

The soft descriptor configuration allows for a transaction description to be shown on the buyer’s credit card statement. This field allows for a 22-alphanumeric-character item description when paying by credit card and up to 15-character description when paying by electronic check. These fields are normally passed via the API; however, they can be set in the UI at the payment gateway or collection group level. The soft descriptor will be passed only for authorization and payment actions.

The soft descriptor field appears as shown:

The following provides additional functionality details:

1. The complete statement descriptor is either a single static descriptor or the combination of prefix and suffix. The suffix is concatenated with the prefix, the * symbol, and a space to form the complete statement descriptor for the customer statement.
2. Aria is allowed to send only the suffix for statement descriptor (soft_descriptor) in the name of statement_descriptor_suffix (maximum of 22 characters), whereas the prefix is sent from the merchant account setting (either statement descriptor or shortened descriptor) in the client’s dashboard (check with Shawn/Integration that the dashboard is a Stripe/client responsibility).
3. Stripe truncates the account statement descriptor as needed to set the prefix value. If the account statement descriptor contains fewer than 10 characters, it is not truncated. The statement descriptor is formed based on the character length of the prefix and suffix.

Some examples appear below:

Note: The statement descriptor must be 5-22 characters including the * symbol and the space, and cannot contain the characters <, >, \, ‘, “, or *.

The following APIs contain the soft descriptor customer service fields:

• create_order_m
• create_order_with_plan_m
• collect_from_account_m
• settle_account_balance_m
• issue_refund_to_acct_m
• authorize_electronic_payment_m

Cardholder-Initiated Transactions/Merchant-Initiated Transactions for Visa® and Mastercard®