Skip to main content
Aria Knowledge Central

create_payment_plan_m Guide

The create_payment_plan_m API creates a new payment plan for an account, allowing the balance to be split into scheduled payments over time.

API Specification:

create_payment_plan_m

Required Fields:

  • <client_no>
  • <auth_key>
  • <acct_no> or <client_acct_id>
  • <client_billing_group_id>
  • <payment_plan_type>

Additional Guidance

  • Aria deprecated the <client_payment_method_id> input field (Release 68, January 2025) and replaced it with the following parameters: <primary_payment_method_no>, <client_primary_payment_method_id>, <backup_payment_method_no>, and <client_backup_payment_method_id>.
  • The payment plan must have a primary pay method before you specify backup pay method.  When attaching a payment method to a payment plan, please add the collection group for this pay method onto the billing group to which the payment plan belongs to.

Input Fields

<do_collect>

Indicates whether the system should collect any amount due today during payment plan creation. If set to true and the collection fails, Aria does not create the payment plan.

For aligned payment plans, Aria will communicate the immediate collection on the account's next anniversary statement. For independent payment plans, Aria does not generate a notification for the immediate collection. 

Aria only collects immediately for these payment methods, with immediate success or failure response:

  • Credit Card
  • Tokenized Credit Card
  • Merchant Gift Card

When you specify a Payment Terms Billing Group and specify <do_collect> = true, Aria creates a payment plan without attempting collection.

Allowable Values

Values Description
true collect immediately
false do not collect immediately (default)
<payment_plan_type>

Allowable Values

Values Description
0 Independent, its own payment plan schedule and due dates
1 Aligned with an existing master plan instance anniversary statement
<payment_plan_period_type>

Allowable Values

Values Description
M Months
W Weeks
D Days
<do_write>

Allowable Values

Values Description
true Performs the requested operation
false Returns potential effects without performing the operation
<all_master_plan_instance>

Include all master plan instances associated with the billing group. If null, it is treated as N (No).

Allowable Values

Values Description
Y Yes, include all master plan instances.
N No, don't include all master plan instances.
<master_plan_instance_balance_ind>

Indicates the master plan instance balance to be paid off with the payment plan. If null, it will be treated as 0 (past due balance). Applicable only if <all_master_plan_instance> = Y, or <master_plan_instance_list> (array) is specified.

Allowable Values

Values Description
0 Master plan instance past due balance.
1 Master plan instance full balance, including amount not due yet.
<payment_plan_lump_sum_type>

Specifies the installment lump sum type for the assigned installment.

Allowable Values

Values Description
P For proportionately split charge/tax.
T For purchase tax only.
<payment_plan_lump_sum_amount_type>

Specifies the lump sum amount type.

Allowable Values

Values Description
P Percentage of balance to be paid.
F Flat amount.
Field Name Notes

Error Codes

Error Code/Description Associated Fields

1001: unexpected error

 

 

1002: no data found

 

1009: account does not exist, Account not found: AriaNo (acct_no), Account not found: Userid (userid), or Account not found: ClientId (client_acct_id)

 

1015: duplicate record found

<client_payment_plan_id>

1016: invalid input

Additional Comments:  This error can be caused by the wrong type of input; for example, text in a numbers-only field, or specifying a value other than one of the documented allowable values.

<aligned_payment_plan_client_master_plan_instance_id>, <payment_plan_type>, <payment_plan_period_type>, <master_plan_instance_id>, <payment_plan_length>, <invoice_list>, <transaction_id_list>

1033:  a parameter that represents a true or false value contains invalid input

<invoice_list>

26003: The API execution is not supported because your client parameter Account_EOM_Enabled is set to False. Please contact Aria customer support with questions about the Account_EOM_Enabled client parameter.

<transaction_list>

32006: Inputs conflict: assign_installment_term input conflicts with client installment term id or installment term no.

TOP
  • Was this article helpful?