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 Paid Plan using Net Terms

Simultaneously Registering a Parent Account and a Child Account with Responsibility Level 2, 3, or 4 for a Paid Plan using Net Terms

This is the recommended process to follow to simultaneously register a parent account and a child account with responsibility level 2, 3, or 4 for a paid plan using the net terms payment method:

  1. Create a parent account and one or more child accounts.
  2. Aria automatically sends the statement to the parent account holder.

Assumptions

The process described in the net terms payment flow for registering a parent account and a child account with responsibility level 2, 3, or 4 for a paid plan deals with:

  • Creating an account with no orders.
  • Making the child account’s billing date the same as the parent account’s billing date.

Preconditions

Use Aria6 to create paid plans. For each paid plan, you must specify the status that an account should have when a customer registers for the plan.

Postconditions

At the end of the account registration process described in the net terms payment flow for registering a parent account and a child account with responsibility level 2, 3, or 4 for a paid plan:

  • A parent account and one or more new child accounts exist.
  • The parent account holder receives a statement.

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 paid plan using the net terms payment method:

parent-child-flow10.png

Notes:

  • Call the create_acct_complete, gen_invoice, get_invoice_details, and manage_pending_invoice methods again for each additional child account that the customer added.
  • The grey boxes indicate functions automatically performed by Aria.
  • If the customer abandons the registration while the account status is billable, Aria continues to generate invoices for the account. You may choose to deactivate the account to prevent additional invoices from being generated.

Instructions

Follow the steps listed below to simultaneously register a parent account and a child account with responsibility level 2, 3, or 4 for a paid plan using the net terms payment method:


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. Set the do_full_invoicing field to false. This prevents the account from being invoiced at this point.
  4. Leave the status_cd field blank. The account status automatically is set based on the status specified in the plan that the customer selected.
  5. Set the master_plan_no field to the number assigned to the master plan that the customer selected for the parent account.
  6. Set the userid field to the user ID that the customer entered.
  7. Set the password field to the password that the customer entered.
  8. Set additional fields based on your company’s requirements.

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

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. Set the do_full_invoicing field to true.
  4. Set the resp_level_cd field to 2, 3, or 4.
  5. Set the senior_acct_no field to the account number of the parent account.
  6. Set the master_plan_no field to the number of the master plan that the customer selected for the child account.
  7. Leave the status_cd field blank. The account status automatically is set based on the status specified in the plan that the customer selected.
  8. Set the master_plan_no field to the number assigned to the master plan that the customer selected.
  9. Set the userid field to the user ID that the customer entered.
  10. Set the password field to the password that the customer entered.
  11. Set additional fields based on your company’s requirements.

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

 

Step 3. Use the gen_invoice call to generate a pending invoice for the parent account.

Preconditions:

  • An account was created.
  • An account number was returned by the create_acct_complete call used to create the parent account.
     
  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 acct_no field to the account number returned by the create_acct_complete call used to create the parent account.
  4. Set the force_pending field to true.

Note: If the pending invoices option is set to false in your Aria implementation, the API call will override the setting in your Aria implementation.

Postconditions:

  • A pending invoice is generated. When an invoice is pending, a collection is not attempted.
  • An invoice number is returned.


Step 4. The get_invoice_details call obtains the details of the invoice generated for the parent account.

Precondition: An invoice number was returned by the gen_invoice call used to generate an invoice for the parent account.

  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 acct_no field to the account number returned by the create_acct_complete call used to create the parent account.
  4. Set the src_transaction_id field to the invoice number returned by the gen_invoice call used to generate an invoice for the parent account.

Postcondition: The invoice details are returned.

 

Step 5. Use the gen_invoice call to generate a pending invoice for the child account.

Preconditions:

  • An account was created.
  • An account number was returned by the create_acct_complete call used to create the child account.
     
  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 acct_no field to the account number returned by the create_acct_complete call used to create the child account.
  4. Set the force_pending field to true.

Note: If the pending invoices option is set to false in your Aria implementation, the API call will override the setting in your Aria implementation.

Postconditions:

  • A pending invoice is generated. When an invoice is pending, a collection is not attempted.
  • An invoice number is returned.


Step 6. The get_invoice_details call obtains the details of the invoice generated for the child account.

Preconditions: An invoice number was returned by the gen_invoice call used to generate an invoice for the child account.

  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 acct_no field to the account number returned by the create_acct_complete call used to create the child account.
  4. Set the src_transaction_id field to the invoice number returned by the gen_invoice call used to generate an invoice for the child account.

Postcondition: The invoice details are returned.


Step 7. Call the gen_invoice and get_invoice_details methods in sequence again for each additional child account that the customer registered for.


Step 8. Obtain the total combined balance of the parent account and child account(s).

Precondition: Invoices were generated for the parent account and child account(s).

Postcondition: The customer confirmed account, plan, and invoice information.

 

Step 9. Use the manage_pending_invoice call to approve the pending invoice generated for the child

account.

Preconditions:

  • The customer confirmed account, plan, and invoice information.
  • The gen_invoice call generated a pending invoice for the child account.
     
  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 invoice_no field to the invoice number returned by the gen_invoice call used to generate an invoice for the child account.
  4. Set the action_directive field to 1 to approve the pending invoice.

Postconditions:

  • The pending invoice for the child account is approved.
  • The balance of the child invoice is transferred to the parent account.

Step 10. Use the manage_pending_invoice call again for any additional pending invoices generated for child accounts.

 

Step 11. Use the manage_pending_invoice call to approve the pending invoice generated for the parent account.

Precondition: The gen_invoice call generated a pending invoice for the parent account.

  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 invoice_no field to the invoice number returned by the gen_invoice call used to generate an invoice for the parent account.
  4. Set the action_directive field to 1 to approve the pending invoice.

Postcondition: The pending invoice for the parent account is approved.


Step 12. Aria sends the statement to the parent account holder.

Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.