Transactions are the heart of the Application

The Transaction object is used to authorize, capture, and refund transactions. Transactions look up to Payment Methods, which serves to select the card or ACH account to process the transaction with.

Transaction Flow

Transaction Status and Payment Status.

Transaction Status and Payment Status.

"Process" is a technical field and you'll only see it after processing a Transaction. Once you refresh, it automatically changes to the next status (Completed or Failed).

Understanding Transactions

Processing a Payment

Only two fields are needed to process a transaction: Amount and Payment Method.

  1. Enter the Amount and Payment Method
  2. Save the record
  3. Click the Capture button.

The minimum charge amount for a USD currency transaction is $0.50. Other currency minimums can be found here

  1. If the Transaction is successful, the Transaction Status = "Completed" and Payment Status = "Captured"

Refund and Partial Refund Transactions

Transactions can be refunded in full or partially refunded. To refund a transaction in full, click on the Refund button. To partially refund a transaction, click on the Partial Refund button, enter the amount to be partially refunded, and click Refund.

Both refunds and partial refunds will create Transactions related to the original, parent Transaction. The Retained Revenue Amount field captures the amount of the Transaction left after all refund(s). Ex. if the original transaction was 100 and two partial refunds of 35 each (70 total) were processed, the Retained Revenue Amount field will read 30.

Failed Transactions

Transactions that fail to process, such as for card declines, cannot be retried. The transaction must be cloned then reattempted. The app is built this way because Stripe maintains IDs, even for failed transactions. payment360 captures the failed transaction ID on the transaction record.

When using our automated Reattempt Logic, new transactions are automatically created when a scheduled transaction fails to process.

Transactions created outside of Salesforce

Transactions that originated outside of Salesforce, such as through a mobile app or web store, will appear in your Salesforce org through Stripe and Blackthorn | Payments’ Webhook Configuration

Batch Processing from a List View

Transactions can be manually processed in batch, with up to 200 at a time through a Salesforce list view. To capture multiple Transactions at one time:

  1. Click on the Transactions tab.
  2. Click on the packaged list view called Scheduled for Auto-Capture (Future).
  3. Select which records to capture by using the checkboxes.
  4. Click on the Capture button.
  5. On the next screen, verify the transactions to process and click on Capture.

Parent/Child Relation to other objects

Transactions can reference any object in Salesforce through the blackthorn | payments Setup configuration. This functionality utilizes the metadata API to automatically create lookup relationships. When an object is selected, a lookup field is created on the Transaction object to the parent object. The Transactions related list will then appear on the parent object (hidden from the page layout by default and must be manually added to applicable parent object page layouts, such as on Opportunity, Case, Order, or a custom object).


Transactions are the heart of the Application