Home > Aria6 User Documentation > Best Practices > Account Registration > Registering Parent-Child Accounts > Simultaneously Registering a Parent Account and a Child Account with Responsibility Level 2, 3, or 4 for a Trial Plan Using an Electronic Check

Simultaneously Registering a Parent Account and a Child Account with Responsibility Level 2, 3, or 4 for a Trial Plan Using an Electronic Check

Overview

A trial plan is a type of master plan that offers your customers a product or service free of charge for a specified time period. You then automatically transfer (rollover) customers to a paid version of the plan. You can create a trial plan with rollover to a paid plan in two ways:

  • Create two different master plans. The first plan is a master recurring plan with no paid services and a duration that you specify. This plan automatically rolls over to a paid plan that you specify. The second plan is a paid plan to which the free plan automatically rolls over after the duration that you specified in the free plan.

For example, you can create a 30‐day trial plan that automatically rolls over to a paid plan on the 31st day.

-or-

  • Create one master recurring plan with paid services in which you specify that a particular number of days is free. After the free period is complete, this free plan automatically becomes a paid plan.

For example, you can create a plan that offers 14 free days and then becomes a paid plan on the 15th day.

Best Practices

This is the recommended process to follow to register a child account with responsibility level 2, 3, or 4 for a trial plan after the parent account was created using a credit card or an electronic check:

  1. Create the child account.
  2. After the completion of the trial period, Aria automatically does the following:
    1. For a plan that is free, then rolls over to a different paid plan:
      • Assign the paid plan to the child account.
    2. For a plan that is initially free, then becomes paid:
      • Update the child account to the rollover status specified in the plan in Aria6.
      • Set the child account’s billing dates based on the date on which the trial period was completed.

For both types of plans mentioned above:

  • Generate an invoice for the child account.
  • Transfer the child account’s balance to the parent account.
  • Generate an invoice for the parent account.
  • Collect the payment from the parent account.
  • Send the statement to the parent account holder.

Note: If the parent account holder is using the electronic check payment (ACH) method, funds might not be available in the customer’s bank account when the collection transaction is settled.

Assumptions

The process described in this flow for simultaneously registering a parent account and a child account with responsibility level 2, 3, or 4 for a trial plan using an electronic check deals with:

  • Creating an account with no orders.

Preconditions

Create your Trial Plans with the Desired Account Statuses

Use Aria6 to create trial plans. For each trial plan, you must do the following:

  • For a plan that is free, then rolls over to a different paid plan, specify:
    • The number of free months that you are offering in the trial plan.
    • The status that an account should have when a customer registers for the trial plan.

Note: This must be a billable status so an invoice can be generated for the child account after the trial period is over.

  • The paid plan to which the trial plan rolls over.

 

  • For a plan that is initially free, then becomes paid, specify:
    • The number of free days or months that you are offering.
    • The status that an account should have when a customer registers for the trial plan.
    • The status that an account should have after the trial period is over and the paid plan goes into effect.

Create your Direct‐Post Configuration Set

To create a Direct‐Post configuration set for parent and child account registration for paid plans using a credit card, define the following name‐value pairs in the set_reg_uss_config_params API call:

  1. Set the client_no field to your Aria‐assigned client number.
  2. Set the auth_key field to your Aria‐assigned authorization key.
  3. Set the set_name field to the name of your configuration set. The name of your configuration set must begin with direct_post_.
    For example, the configuration set could be named direct_post_paidreg.
  4. Set the redirecturl field in the in_reg_uss_config_params array to the URL in your account registration application where you display error or success messages. These messages are sent by Direct Post.

    Setting this field causes Direct Post to trigger the update_ acct_ complete call to set the payment method of the parent account to credit card.

Postconditions

At the end of the account registration process described in the electronic check payment flow for simultaneously registering a parent account and a child account with responsibility level 2, 3, or 4 for a trial plan:

  • A parent account and one or more new child accounts exist.
  • After the completion of the trial period:
    • The child account’s billing dates are set.
    • A payment is collected from the parent account.
    • The parent account holder receives a statement.
    • If collection fails, the account goes into dunning.

Process Flow Diagram

The diagram below illustrates the recommended process for simultaneously registering a parent account and a child account with responsibility level 2, 3, or 4 for a trial plan using an electronic check:

parent-child-flow7.png

Notes:

  • Call the create_acct_complete method again for each additional child account that the customer added.
  • The light grey boxes indicate functions automatically triggered by Direct‐Post based on your configuration set.
  • The dark grey boxes indicate functions automatically performed by Aria.

Instructions

Follow the steps below to register an account for a customer who is signing up for a parent account and a child account with responsibility level 2, 3, or 4 at the same time for a paid plan:

Step 1. Use the create_acct_complete call to create the parent account.

Precondition: A customer visits your website and signs up for a parent account and one or more child accounts in the same sitting.

  1. Set the client_no field to your Aria‐assigned ID number.
  2. Set the auth_key field to your Aria‐assigned authorization key.
  3. Leave the status_cd field blank. The account status is automatically set based on the status specified in the plan that the customer selected.
  4. Set the do_full_invoicing field to false. This prevents the account from being invoiced at this point.
  5. Set the master_plan_no field to the number of the master plan that the customer selected for the child account.
  6. Set the userid field to the customer’s user ID.
  7. Set the password field to the customer’s password.
  8. Set additional fields based on your company’s requirements.

Note: It is not recommended that you set the bank account fields using the create_acct_complete call. It is recommended that you use Direct‐Post to set the bank account fields as described in Step 5.

Postcondition: The account is created and an account number is returned.

 

Step 2. Use the create_acct_complete call to create a child account.

Precondition: A customer visits your website and signs up for a parent account and one or more child accounts in the same sitting.

  1. Set the client_no field to your Aria‐assigned ID number.
  2. Set the auth_key field to your Aria‐assigned authorization key.
  3. Leave the status_cd field blank. The account status is automatically set based on the status specified in the plan that the customer selected.
  4. Set the do_full_invoicing field to false. This prevents the account from being invoiced at this point.
  5. Set the resp_level_cd field to 2, 3, or 4.
  6. Set the senior_acct_no field to the account number of the parent account.
  7. Set the master_plan_no field to the number of the master plan that the customer selected for the child account.
  8. Set the userid field to the customer’s user ID.
  9. Set the password field to the customer’s password.
  10. Set additional fields based on your company’s requirements.

Postcondition: The account is created and an account number is returned.

 

Step 3. Repeat Step 2 for each additional child account that the customer added.

Step 4. Use the set_session call to obtain an Aria session ID for Direct Post.

Precondition: A parent account and one or more child accounts were created.

  1. Set the client_no field to your Aria‐assigned ID number.
  2. Set the auth_key field to your Aria‐assigned authorization key.
  3. Set the user_id field to the user ID that the customer entered for the parent account.

Postcondition: An Aria session ID for Direct‐Post is obtained.


Step 5. Transmit bank account information from your payment information page to Direct Post.

Preconditions:

  • You created a Direct Post configuration set for trial plans.
  • An Aria session ID for Direct Post was obtained.
  • The customer entered bank account information for the parent account.

Transmit the following fields and values from your payment information page to Direct‐Post:

  1. Set the mode field to the suffix of the configuration set that you created.

For example, if you named your configuration set “direct_post_cctrialplan”, then you would set the mode field to “cctrialplan”. The mode field is a hidden field.

  1. Set the inSessionID field to the session ID returned by the set_session call. The inSessionID field is a hidden field.
  2. Set the client_no field to your Aria‐assigned client number. The client_no field is a hidden field.
  3. Set the formOfPayment field to ACH.
  4. Set the bank_routing_num field to the bank routing number that the customer entered.
  5. Set the bank_acct_num field to the bank account number that the customer entered.

Postcondition: The session ID is returned.


Step 6. Direct‐Post triggers secure bank account transactions based on your configuration set.

Precondition: Bank account information was transmitted from your payment information page to Direct‐Post.

Direct Post does the following:

  1. Verifies the validity of the session.
  2. Validates the bank routing number.
  3. Sets the payment method of the account to ACH.

Note: If an error occurs after Steps b or c above, then redisplay the payment information page and repeat the process beginning with Step 5.

Postconditions:

  • A session ID is returned.
  • The bank routing number is validated.
  • The payment method of the parent account is set to ACH.


Step 7. After completion of the trial period, Aria automatically does the following:

  1. For a plan that is free, then rolls over to a different paid plan:
  • Assigns the paid plan to the parent and child accounts.
  1. For a plan that is initially free, then becomes paid:
  • Updates the parent and child accounts to the rollover status specified in the plan in Aria6.
  • Sets the parent and child accounts’ billing dates based on the date on which the trial period was completed.
  1. For both types of plans mentioned above:
  • Generates an invoice for the parent account.
  • Collects the payment from the parent account.
  • Sends the statement to the parent account holder.
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
Powered by CXone Expert ®