Summary

In some licensure programs, employers are responsible for paying their employee's credentialing fees. The "3rd Party Payment Queue" is a feature of the Organization Portal that allows a responsible party to make a single credit card payment that satisfies the Payment attribute on multiple Workflow Instances.

Business Case

Organizations that have large numbers of credential Applicants or credential holders benefit from being able to pay for Application fees on behalf of their employees.

The Bulk Payment option allows Organizations to make a single payment for all Applicants who have payments available to them.

Scenarios that benefit from this scenario:

Employers with many employees who may apply at any time;
Employers that wish to pay for Applications via credit card;
Employers that do not wish to track which Applicants;
Employers who do not wish to or cannot negotiate organization-specific rates (e.g., licensure);

Use Stories

The following user stories apply to this scenario:

As an Employee, I specify my Employer;
As an Employee, I reach the payment step of a Workflow;
As an Employee, I pause my Application without paying;
As an Organization Contact, I find all the Applications for my Employees;
As an Organization Contact, I select all the Employees whose Application fees I wish to pay;
As an Organization Contact, I complete a credit card purchase for all those selected;
As the System, I trigger that payment has been received on all affected Applications, and perform any behaviors necessary to move those Applications to their next step.

Configuration

Use a Supervisor attribute to establish the supervisory relationship between the user owning the Workflow Instance with the Payment attribute and the person/organization that will be making the bulk payment;
Grant the person/organization making the payment the Responsible Party → AccessPendingPaymentQueue permission

The supervisor Member should be able to access Responsible Party → Pending Payment Queue to view a list of all supervisee Workflows that are currently on a Step with a Payment. From this queue the supervisor can bulk-select the ones to pay and make a credit card payment.

Requirements

LearningBuilder 9.0
A supervisory relationship (via a Supervisor attribute) exists between the Organization making the payment and the Practitioners that own the Workflow Instances containing the Payment attributes that need to be paid
Only Workflow Instances on a Step with a Payment attribute can be selected for and included in the 3rd-party payment.
The user making the payment must have the Responsible Party → AccessPendingPaymentQueue permission.

See Also

Related articles

Page:
Bulk Employer Payments (LearningBuilder Documentation)
- payments
- third-party-payments
Page:
Discount Codes (LearningBuilder Documentation)
- payments
- third-party-payments
Page:
Tenant-Specific Payment Settings (LearningBuilder Documentation)
- payments
- third-party-payments
Page:
Third-Party / Employer Payments (LearningBuilder Documentation)
- payments
- third-party-payments