Core Concepts
Money Concepts
Forge handles ticket pricing, discount codes, fees and payment capture for paid events. Charging from Forge works with Stripe, Authorize.net and Spreedly gateways. All financial records live in Salesforce in the Blackthorn Payments package (bt_stripe__); Forge never stores card numbers or payment instrument data.
The money chain, in order
| Step | Record | What it is | Where you see it |
|---|---|---|---|
| 1 | Ticket (Event Item) | What is for sale, with a price or Free. | Event > Tickets |
| 2 | Invoice / Order (Sales Document) | The bill for one purchase: line items, discounts, fees, tax, total and balance. | Event > Finance > Invoices |
| 3 | Transaction | One movement of money against an invoice: a charge, capture, refund, reversal or write-off. | Event > Finance > Transactions |
| 4 | Allocation | How a payment is split across invoices and line items. | Event > Finance > Allocations |
Ticket pricing
Each ticket (conference360__Event_Item__c) has a Price, a Free checkbox and a Status. If Free is on, or the price is 0, no payment is collected. An event can mix free and paid tickets; the payment step is skipped only when the attendee's total is zero. A paid ticket cannot be purchased until a payment gateway is selected for the event. Enter prices before tax: tax and fees are added at checkout.
Fees and tax
A Fee is an extra charge added at checkout: either a payment processing fee passed on to registrants, or tax. Fees are set per event under Tickets > Fees (shown when Fees is enabled for your org), not in a global template.
| Fee field | What it does | Recommendation |
|---|---|---|
| Type | Tax or Payment Processing. Tax is applied to the total after discounts. Payment processing fees are applied after tax. | Use Tax for sales tax or VAT and Payment Processing to pass on card costs. |
| Fee Percentage | The percentage value of the fee. | Match your gateway's rate if you pass costs on. |
| Default Fee | If checked, this fee is the default. Checking it unchecks any existing default. | Make your most common fee the default. |
| Tax Display Setting | Tax-Inclusive Pricing puts tax inside the advertised price. Calculated at Checkout shows tax only on the final payment screen. Taxes always show as a separate line at payment. | Use Tax-Inclusive where prices are advertised with tax (for example VAT); use Calculated at Checkout elsewhere. |
Discount and promo codes
Codes are created on the event under Tickets > Discount Codes. To limit a code to certain tickets, set its scope to Ticket and pick them from the list, which always shows the event's current tickets.
| Code field | What it does | Recommendation |
|---|---|---|
| Type | Discount lowers the amount. Access-Promo unlocks the ability to buy an item or gives a promotional benefit. Source is a tracking code that follows a visitor, such as in an embedded link. | Use Access-Promo for member-only tickets and Source to see which campaign sent registrants. |
| Discount Amount / Discount Percentage | A fixed amount off, or a percentage off. | Use a percentage for early-bird promotions and an amount for a fixed voucher. |
| Quantity Made Available | How many times the code can be used. Blank means unlimited. Quantity Claimed counts uses and Quantity Remaining is the difference; the code stops working when claimed equals available. | Set a limit for scarce promotions. |
| Valid From / Valid Through | The code works on or after the first date and on or before the second. | Set both for a time-limited offer. |
| Restrict To Account | Only Contacts associated with that Account can use the code. | Use for corporate or partner discounts. |
| Forge | SF Object | SF Field |
|---|---|---|
| Fee type | bt_stripe__Fee__c | bt_stripe__Type__c |
| Fee percentage | bt_stripe__Fee__c | bt_stripe__Fee_Percentage__c |
| Discount code type | bt_stripe__Code__c | bt_stripe__Type__c |
| Discount amount | bt_stripe__Code__c | bt_stripe__Discount_Amount__c |
| Discount percentage | bt_stripe__Code__c | bt_stripe__Discount_Percentage__c |
| Uses available | bt_stripe__Code__c | bt_stripe__Quantity_Available__c |
| Invoice status | bt_stripe__Sales_Document__c | bt_stripe__Status__c |
| Invoice payment status | bt_stripe__Sales_Document__c | bt_stripe__Payment_Status__c |
| Transaction status | bt_stripe__Transaction__c | bt_stripe__Transaction_Status__c |
| Transaction payment status | bt_stripe__Transaction__c | bt_stripe__Payment_Status__c |
Invoice and payment fields
| Field | What it means | Recommendation |
|---|---|---|
| Invoice Status | Where the invoice is in its life: Draft (default), Sent, Accepted, Completed, Rejected, Voided, Ready To Bill, Uncollectible. | Void an invoice you issued in error rather than deleting it. |
| Invoice Payment Status | How much has been paid: Unpaid, Past Due, Partially Paid, Paid, Refunded, Partially Refunded, Overpaid. Set automatically. | Do not set it by hand; record a transaction instead. |
| Total, Subtotal, Balance Due, Balance Paid | The invoice amounts. Balance Due is what is still owed. | Use Balance Due to chase unpaid registrations. |
| Transaction Status | The state of the transaction, which drives business logic: Open (default), Process, Pending, Pending Payment Intent, Completed, On Hold, Canceled, Needs Review, Failed. Only Open and Canceled should be set by hand. | Leave all other values to the payment process. |
| Payment Status | The state of the funds, meaningful only when Transaction Status is Completed: Authorized, Captured, Partially Captured, Refunded, Partially Refunded, Uncaptured, Disputed, Dispute Warning, In Transit, Paid, Transferred, Partially Reversed, Reversed. | Authorized funds become Uncaptured after 7 days if not captured, so capture promptly. |
How Forge dashboards count money
| Figure | Definition | Where |
|---|---|---|
| Revenue | The sum of order totals (invoice totals) for the event or events. | Home, Reports, event Reporting |
| Captured (cash collected) | Transactions whose payment status is captured, paid or settled. | Reports > Finance |
| Authorized | Funds held on a card but not yet captured. | Event finance |
| Refunds | Transactions whose status is a refund. | Reports > Finance |
| A/R (outstanding) | Order totals minus captured minus refunds. Authorized amounts are not subtracted, because they will be captured later. | Reports > Finance |
If Revenue and Captured differ, the gap is A/R: orders not yet paid. A large Authorized amount means captures are pending.
Payment gateways
Forge can connect and charge through Stripe, Authorize.net, TouchNet, and other providers via Spreedly (for example PayPal's PayFlow Pro) today. CashNet can be connected in Admin > Payment Gateways, but Forge cannot charge through it yet, so refunds and other money movement for CashNet stay in Salesforce. Gateways are configured in Admin > Payment Gateways and stored as bt_stripe__Payment_Gateway__c records. You can have multiple gateways configured and assign a specific gateway per event.
Card data never touches Forge or Salesforce
Payment card numbers, CVVs, and bank account details are handled exclusively by the payment gateway (e.g., Stripe's iframe / Stripe.js). Forge and Salesforce never see, transmit, or store raw card data. Transaction records in Salesforce contain only the charge amount, status, and a gateway reference ID.
Recurring billing
Recurring payments (for donations or membership-style tickets) run on Blackthorn's own recurring engine — bt_stripe__Payment_Schedule__c records processed by scheduled Apex in Salesforce — rather than the gateway's native subscription billing. Forge never uses Stripe Subscriptions or Stripe Billing. Payment schedules are configured on the Salesforce side today; Forge does not yet have an admin toggle that sets them up for you.
Refunds
A refund is sent to the payment gateway from the event's Finance > Transactions list: choose Refund on a transaction, pick Full or Partial refund, an amount that cannot exceed the original, and a reason (Requested by customer, Duplicate charge or Fraudulent). The original becomes Refunded or Partially Refunded and the refund is recorded as its own linked transaction. Refunding from Forge works through the payment gateway tools, which must be turned on for your org. A refund does not by itself cancel the registration, remove the attendee or change the invoice line items: update the attendee's Registration Status and the invoice separately if you need those to follow.
A refund is submitted to the gateway immediately. How quickly the cardholder sees the money depends on their bank.