Overview
A Payment Type tells fusionCore how money can move for a part of your organization. Each one names a payment method (such as Card, Check, or Account Credit), says where it can be used, and controls whether it can issue refunds. Each Payment Type you create is one record in thePayment_Type__c custom object. These records are configuration, not transactions. The actual money movement is recorded separately on Financial Event (Financial_Event__c) records when staff or members pay or refund.
You set up a Payment Type for a Business Unit (Business_Unit__c), which is a branded operating division of your organization. This lets you control exactly which payment options appear, per division and per currency. For example, you can offer “Card via Stripe” to portal members, restrict “Check” to back-office staff, and offer “Account Credit” to both.
Payment Types are the main lever you pull when the right payment option is not showing up on a pay or refund screen. Most “my payment method is missing” problems trace back to a Payment Type’s settings — see the Limitations and Common Pitfalls section on the category page for your method.
Payment Type Categories
There are three categories of Payment Type. Each category page walks through its full setup — the fields to set, the components it uses, and the rules enforced when you save.Online (Stripe) Payment Types
Stripe-backed Card and ACH methods that can appear in the portal and be saved as wallet items.
Offline Payment Types
Staff-only Check, Cash, and Account Credit methods that do not use a payment processor.
Custom Payment Types
Add a payment method beyond the built-in options, which needs extra configuration.
Record Types
Payment_Type__c has two record types:
When you click New, Salesforce asks which record type you want. Choose Payment for a checkout option, or Wallet Item for a saveable stored method.
Before You Begin
Before you can create or edit Payment Types, an admin must assign you the right permission set.
For Stripe orgs, staff who pay or refund also need
FC_Stripe_Access or FC_Stripe_Manage.
Fields on a Payment Type
The category pages walk through setup for each category. The table below is the shared field reference for all of them.The component fields (
Payment_Component__c, Refund_Component__c, Wallet_Item_Component__c) are not on the default page layout. The category pages explain which component each method uses and how to set them.How Paying and Refunding Work
Payment Types control which options appear in the runtime flows; they do not move money themselves.- Paying: Staff pay from an Order using the Pay Order quick action, or from a Financial Event using Pay. Members pay through the portal checkout. On success, fusionCore creates a Financial Event (
Financial_Event__c) with its event lines, and, for provider-backed payments, a parallel Payment Provider Event (Payment_Provider_Event__c). - Refunding: Staff refund from a Financial Event using the Refund quick action, then enter the amount and choose a method. The methods on offer depend on the original payment and on each Payment Type’s Refund Behavior.
Related Features
Taking and refunding a Stripe payment
Walk through paying and refunding an Order with Stripe.
Business Units
Every Payment Type belongs to a Business Unit and deposits into that unit’s GL Accounts.
Stripe
Provider-backed Payment Types link to a Stripe Payment Provider Account.
Paying on an Order
Where the Payment Types you configure appear in the staff pay flow.
Account Credit
The Account Credit payment method is offered through an Account Credit Payment Type.
Installments
Installments require a provider-backed, wallet-eligible Payment Type to charge over time.
Wallet item page (Portal)
Wallet Item Payment Types let portal members save a card or bank account to reuse.