ePayments

Locating the ePayments History feature

Anyone in a Role with the ePayments privilege to edit Forms in a program with ePayments enabled can add ePayment functionality to Forms and can visit a log of past payments by opening the ADMIN menu and clicking on ePayment History:

How to add ePayments

ePayments

PowerClerk supports integrated ePayments via secure integration with Stripe (www.stripe.com). Stripe integration is the default and preferred ePayment option in PowerClerk. In addition to Stripe, we have incorporated Paymentus, KUBRA EZ-PAY, and J.P. Morgan-hosted PayConnexion on a selective basis. The ePayments feature is fully integrated into PowerClerk’s Forms, Workflow, and more to enable the Program Designer to determine which Form(s) require payment and whether payment is required in order to submit the Form(s). Transactions are processed in seconds (via iFrame – see Figure 1 below) without the need for the user to navigate away from PowerClerk to pay. Payment confirmation is presented to the payer and the Administrator in real time in the PowerClerk web user interface. Automatic notifications are sent to the payer in real time (and can be sent to the Utility if needed), and payment status reporting can be run from Stripe which provides real time results as well.

Clean Power Research is not directly involved in the transaction. The PowerClerk utility/agency establishes a Stripe account, which includes provisioning of a merchant account, in minutes. Credit card payments from applicants (less fees) will be deposited directly into the merchant account. Credit card transactions are between the applicant and the PowerClerk utility/agency customer; the funds never touch any Clean Power Research bank account. CPR will have neither visibility nor access to the merchant account. The PowerClerk utility/agency customer is responsible for transferring funds out of the merchant account into the account of their choosing, and transfers can be as frequent as rolling two-day basis. The PowerClerk utility/agency customer tracks incoming payments, issues refunds as needed, and manages transfers and reporting all from their Stripe account. Use of ePayments involves transaction fees by the payment platform (Stripe) and Clean Power Research.

Stripe’s transaction fees ($0.30 + 2.9% per transaction) are levied directly against each transaction amount during processing. For example, for a $50.00 ePayment charge, $48.25 will enter the merchant account, and $1.75 will go to Stripe. PowerClerk’s ePayment fees can be flat (fixed amount) per Form, or Formulas can be used to dynamically calculate the application fee amount.

The sole payment method available via the ePayments feature today is credit card.

PowerClerk provides an ePayment tab as the last page of any Form for which ePayments has been enabled. This will encapsulate the credit card information and pre-payment confirmation experience. This will take over the “Submit” experience of a Form (as in the Form with required ePayments cannot be submitted until payment is complete) and provide a payment confirmation summary upon completion of the payment process.

Stripe provides PowerClerk a transaction identifier for each transaction to make it easy for the Admin to track payment history per project from the Admin page (see Figure 3):

How to set up ePayments

To process Stripe payments through PowerClerk you will need to connect the Stripe account to your production PowerClerk program. This process entails the following steps outlined below. Once the accounts are connected you will need to configure your payment forms so that ePayments are enabled.
 
Stripe Dashboard:
 

Figure 5: Stripe Dashboard

To Connect the Stripe account to your PowerClerk program:
1. Log in to PowerClerk and Stripe
2. From the Admin page, select “Connect with Stripe”:
    

   

   Figure 6: Connect with Stripe

    

3. Click the button to “Connect with Stripe” and follow the instructions:
    

   

   Figure 7: Connect with Stripe Button

    

After you connected with Stripe, please select from the Forms page the form you wish to enable ePayments for and click on Configure Form:
 

Figure 8: Configure Form

 
Then follow these steps to complete your Stripe setup:

1. Enter a Charge description (optional)
2. Determine when payments are required (Only the First Time Form is Submitted or Always)
3. Select the Calculated Field to calculate the amount

Figure 9: Configuring Forms

FAQs

Q: Why does my "Payment ID" field remain empty while testing my Stripe payment process.

A: Stripe does not generate receipt numbers during test runs, since receipt emails are not sent out during testing. Once released to production, the Payment ID field will show the correct information as expected.

Figure 8: Empty Payment ID field during testing.

Q: I would like to round the display of a decimal field within my Document Template; is this possible?

A: Yes, you are able to round the display of decimal data fields within Document Templates by using the following convention:


For example you can round a decimal value of 100.12345678999 to 3 digits after the decimal sign by using {data: datafield,,3} which will then display in your Document Template as "100.123". This won't effect the data fields actual value stored within the database, where you will retain the full standard precision of 10 digits after the decimal sign.

Have additional questions? Contact us to nominate your FAQ and help others find answers to your own questions concerning this feature.

Create A Support Ticket

Not finding your answer here?  Submit a question to our support team at the PowerClerk Ticket System and leverage the PowerClerk team’s expertise.