Platform Configuration
How exactly does this happen? We're glad you asked, because it's pretty cool! An encrypted code, called a JWT (Json Web Token) is handed off to each payment vendor from the Invoice Details & Payment widget. This code contains information about the transaction, including the total due, and payer. The vendor processes the user's transaction and then hands an updated JWT back, where the user is redirected to the Invoice Detail widget. The JWT is created at the moment a User clicks Pay Now.
It's important to note that the Portal and Widgets handle payments differently. In the Portal, the payment information was collected, processed by your payment processor, and returned. This meant that the transaction happened on your server and PCI compliance was required. Any features added would be independent of your giving vendor.
In Widgets, the invoice is handed to your payment processor, processed by your payment processor, and returned. This means the transaction happens on your vendor's end (No PCI compliance required!) and the end user has the same experience as they do when they give online (for example, saved credit cards).
Verified Vendors
Product Options
Registration details are controlled by the Online Registration Product. A few things to note:
- Product Option Group Note Label: Displays before each option price.
- Product Option Prices Max Quantity: Max quantities for your Product Option Prices are dependent on two criteria:
- The Product Option Price is part of a non-canceled Invoice, AND
- The Product Option Price is associated with a "registered" Event Participant. If the invoice is not paid within an hour of creation, a process will cancel the invoice and Event Participant record. The canceled Event Participant record will not be counted toward the max quantity of the Product Option Price.