Search the Aria Knowledgebase for
User Documentation, APIs, SDKs, and more!

 

Home > Aria Crescendo Documentation > Direct Post Payment Handler > Create Direct Post Configuration

Create Direct Post Configuration

Table of contents
This article applies to:Aria Crescendo

Overview

Direct Post is required for Aria clients who are not PCI compliant and who collect credit card and ACH information from customers as part of the payment process. With Direct Post, Aria’s clients can host all payment pages in their Aria‐centered applications with full PCI security compliance. Payment information is never seen, processed by, or stored on their systems. Credit card and bank account numbers entered on payment pages pass directly from the customer’s browser to Aria using encrypted post, without the need to host pages on Aria’s PCI compliant infrastructure.

To define a Direct Post configuration in the UI, navigate to Configuration > Client Settings > USS Reg Configuration > New Direct Post

The fields on this screen are as follows:

Set Name: Name of the collection of Direct Post configuration values you are entering on this screen.

Set Description: Description of the collection of Direct Post configuration values you are entering on this screen.

Redirect URL: This is a URL to which the Direct Post Handler immediately redirects once it has processed payment information. It must be capable of performing error handling based on the potential error messages that the Direct Post Handler can return, or capable of printing a "receipt page" (or some other type of success page) if there are no returned errors.

One Time Collection: A User Self Service (USS) feature that uses a form input field called “collection_amount”. If an amount is not provided, the account balance is collected. Only use this field in conjunction with Credit Card and Automated Clearing House (ACH) forms. Net Terms is not supported, so any form of Net Terms should not be selectable in this type of payment page. If this is set to True, collection is performed using the amount entered in the “collection_amount” form field (or if blank, the entire account balance), with the entered Credit Card or ACH information. Form of payment on file is not changed. There must be a positive numeric value entered in the “collection_amount” field. If set to True, this takes priority over all other directives, which are not used. Payment is processed at the account level and applied to open charge transactions in a First In, First Out (FIFO) manner.

Minimum Credit Card Authorization Threshold: Minimum transaction amount above which credit card authorization must occur. For instance, if you want a minimum $10 balance before authorizing an electronic payment, set this to 10. This threshold is honored for authorizations performed regardless of whether Perform Both Authorizations and Collections for Credit Cards is set to True or False. If not specified, a minimum authorization threshold of 1 is used.

Use Full Amount When Authorizing Credit Cards: Determines whether a full authorization or a $0 authorization is performed for credit card payment methods. Note that <min_cc_auth_threshold> is honored for both full authorizations and $0 authorizations.

Minimum Collection Threshold: Minimum balance amount above which collections occur. For instance, if you want at least $10 of transactions to occur before collecting an electronic payment, set this to 10. If not specified, a minimum collection threshold of 1 is used.

Perform Both Authorizations and Collections for Credit Cards: Determines whether to perform both an authorization and collection when a credit card is provided. Note that the Minimum Collection Threshold is honored for all collection attempts, so in cases where the amount to be collected falls below the Minimum Collection Threshold, no collection is performed.

Change Master Plan Instance Status on Success: Indicates that the master plan instance status is changed if the collection or authorization performed as part of the Direct Post process succeeds. Set it to False if you do not want to change the master plan instance status.

Master Plan Instance Status on Success: If Change Master Plan Instance Status on Success is set to True, select the new status for the Master Plan Instance from the drop-down menu. See Master Plan Status Codes for a description of plan statuses.

Change Master Plan Instance Status on Failure: Indicates that the master plan instance status is changed if the collection or authorization performed as part of the Direct Post process fails. Set it to False if you do not want to change the master plan instance status.

Master Plan Instance Status on Failure: If Change Master Plan Instance Status on Failure is set to True, select the new status for the Master Plan Instance from the drop-down menu. See Master Plan Status Codes for a description of plan statuses.

Disable Payment Method on Failure: By default, the payment method provided using Direct Post is saved as an active payment method on the account in Aria. In cases where the collection or authorization fails, this parameter determines whether the payment method remains as an active payment method on the account, leaving it available for future use. Set this to True to disable payment methods in cases of authorization or collection failures, making the payment method unavailable for future use.

Save Credit Card as Token: For payments made using credit cards or debit/check cards that are processed as credit cards, this flag indicates if the card number is stored as a token by the processor.

Kill Direct Post Session: If this field is set to True, Direct Post calls the kill_session API method, which disables the current session ID after Direct Post has completed its transactions, either successfully or unsuccessfully. After the session ID is disabled, you must call set_session_m or set_session_auth_m again to start a new session if you want to retry any unsuccessful transactions. This allows you to verify the validity of a session every time a customer resubmits payment information. In addition, disabling a session ID prevents that session ID from being used for any transactions other than the ones triggered by Direct Post in your Account Registration or User Self Service application. If this field is set to False, the Direct Post session is not killed. This allows the same session to be reused if a customer attempts to resubmit payment information.

Note: If you call the set_session_m or set_session_auth_m API method for something other than Direct Post and you want to utilize the <kill_dp_session> field, you must call a separate instance of set_session_m or set_session_auth_m specifically for Direct Post. For example, if you set up the <kill_dp_session> to automatically disable a session ID, when Direct Post attempts to authorize a credit card and the authorization fails, the session ID is disabled. You must then call set_session_m again to start a new session and allow the customer to resubmit credit card information.

Alternative Client Group ID: Specifies the Client Group ID, a unique ID code that identifies a collection account group. You add a Client Group ID when you create or edit a collection account group in Aria. This ID specifies that, for the current payment, Aria processes the transaction using the payment gateway information associated with the corresponding collection account group. This collection account group is used instead of the default Aria collection account group or the collection account group to which a customer is assigned.

Note: Using this field does not assign a customer to the corresponding collection account group. Future payments will be processed using the default Aria collection account group or the collection account group to which a customer is assigned.

You must to post a comment.
Last modified
16:19, 26 Aug 2016

Tags

Classifications

This page has no classifications.