To begin using RunPayments with TRUE, you will work directly with the RunPayments support team to establish your merchant account and obtain your credentials.

1. Contact RunPayments to begin the merchant account application process
2. Complete the required business documentation and underwriting requirements with Fiserv
3. Your RunPayments account manager will provide your production credentials once approved
4. Receive your Run Merchant Welcome Email and activate your Run Merchant portal account
5. Configure your credentials in TRUE Company Preferences (see below)

Connect your RunPayments account to TRUE by entering your credentials in Company Preferences. This is the only setup required within TRUE.

1. Click the Gear icon and select Company Preferences
2. Navigate to the Integrations section
3. In the Payment Processing area, set the gateway to Card Connect
4. Enter your credentials in the fields below
5. Save your preferences to enable RunPayments across all payment modules

The following credentials are required to activate RunPayments. Your RunPayments account manager will provide all of these values.

Once RunPayments is activated, the standard TRUE payment processing settings apply. These are configured in the same Company Preferences > Integrations section.

RunPayments supports all major credit and debit card networks. Card payments can be processed through:

• Point of Sale — Click Add Card and enter the card number directly into the RunPayments card number field
• Transaction Wizard — For keyed-in phone orders and office payments
• ePay Links — Customers enter their own card details through a secure payment link
• CardPointe Terminal — For card-present swipe/chip transactions (if terminal is configured)

When a valid card number is fully entered, RunPayments will automatically detect the card type. If credit card fees are enabled in Company Preferences, the fee amount will display before processing.

ACH payments allow customers to pay directly from their bank account. In TRUE, ACH payments are processed through the same Point of Sale window.

1. Open Point of Sale and select the bank/ACH payment option
2. Click Add Bank
3. Enter the routing number and account number in the format: routing number / account number
4. Process the transaction

• ACH transactions typically have lower processing fees than credit card payments
• ACH transactions may take 2–3 business days to clear
• ACH transactions appear in the Run Merchant portal for tracking

Send customers a secure link to pay invoices or quote deposits online. The ePay workflow is the same as with Stripe.

1. From an Invoice or Quote, select the option to email the document
2. Enable the Include ePay Link option in the email dialog
3. The customer receives an email with a secure payment link
4. Clicking the link opens a payment form where they can enter card or bank information
5. Once payment is complete, TRUE automatically records the payment against the invoice

RunPayments supports secure token storage, allowing you to save customer payment information for future transactions — similar to how Stripe handled stored cards.

• When a customer pays, their card information can be tokenized and stored securely
• Actual card numbers are never stored in TRUE — only secure tokens
• Returning customers can have their stored token used for subsequent transactions
• Stored payment details are also accessible through the Vault section in the Run Merchant portal

The Run Merchant Dashboard provides a snapshot of your account's payment activity.

• Volume Chart — View processed volume over time (daily, monthly, etc.) and compare across multiple merchant accounts
• Daily Summary Cards — Quick counts for transactions, volume, refunds, chargebacks, and batch funding
• Funding Card — Insights on deposit activity
• Statements Download — Download credit card or ACH statements directly from the dashboard
• Chargeback Manager — Quick access to dispute chargebacks

Use the filters at the top of the dashboard to change the date range or filter by specific merchant accounts/locations.

The Reporting > Transactions section displays all transactions tied to your merchant account. This is where you verify payment status, review transaction details, and perform refunds.

Click any Transaction ID to open the Transaction Detail page, where you can:

• View full transaction details — Card type, amount, status, auth code, batch ID, and more
• Reverse/Refund — Issue a full or partial refund directly from the portal
• Send Receipts — Email a receipt to the customer with an optional custom message
• View transaction history — Time-stamped list of all status changes for that transaction

Reports can be filtered by MID/account, date range, and keywords. Use the Download button to export any report as CSV.

The Funding report lists all deposits made to your bank account from processed transactions.

Click any Deposit ID to view funded batches, individual transactions within the funding event, and any rejected transactions.

The Chargebacks section displays all chargebacks submitted by cardholders to dispute transactions. You can review, track, and dispute chargebacks directly from the Run Merchant portal.

To dispute a chargeback:

1. Navigate to Reporting > Chargebacks in the Run Merchant portal
2. Click the chargeback you want to dispute
3. Fill out the dispute form with supporting documentation
4. Submit the dispute for processing

The Vault stores saved customer payment information. Vaulted customers can be charged quickly without re-entering payment details, both from within TRUE and from the Run Merchant portal directly.

From the Vault page, you can:

• View saved payment details — Last 4 digits, card type, expiration, and associated MID
• Edit vault details — Update customer information or payment method
• Charge a vaulted customer — Opens the Virtual Terminal pre-filled with the customer's details
• View associated transactions — See all past transactions for a vaulted customer
• Delete a vault record — Remove saved payment information

Merchant account statements are available in the Statements tab, separated by Credit Card and ACH statements. Statements can be downloaded and saved for record keeping.

You can create additional user accounts for access to the Run Merchant portal under Settings > Users.

New users receive a Run Merchant Welcome Email with instructions for setting up their account.

1. Contact RunPayments to begin the merchant account application and onboarding process
2. Once approved, your RunPayments account manager will provide your site name, API credentials, and merchant ID
3. Navigate to Company Preferences > Integrations > Payment Processing
4. Change the gateway from Stripe to Card Connect
5. Enter your RunPayments credentials (Site, Username, Password, Merchant ID)
6. Test a small transaction to verify the integration is working correctly

You need four pieces of information, all provided by your RunPayments account manager:

1. Site — Your RunPayments site name (usually "runpayments" by default)
2. Username — API account username
3. Password — API account password
4. Merchant ID — Your unique merchant identifier, available from your account manager or Run Merchant portal

Once these four values are entered in Company Preferences > Integrations with the gateway set to Card Connect, RunPayments is active and working.

RunPayments operates on the CardConnect payment gateway, which is powered by Fiserv. In TRUE, the gateway dropdown displays "Card Connect" because that is the name of the underlying payment processing gateway. Selecting Card Connect and entering your RunPayments credentials is how you activate the RunPayments integration.

If the ePay link option is not appearing when emailing invoices:

1. Verify that RunPayments is properly configured in Company Preferences > Integrations
2. Confirm all four credential fields are filled in (Site, Username, Password, Merchant ID)
3. Ensure the gateway is set to Card Connect
4. Contact TRUE Support if the option still does not appear after verification

From the TRUE user's perspective, the functionality is the same — both processors support credit card payments, ACH, ePay links, token storage, and terminal devices. The differences are:

• UI differences — The payment input fields look slightly different, but the workflow is identical
• Input requirements — Stripe requires more detail (CVV, expiration) for keyed-in transactions; RunPayments requires only the card number
• External portal — RunPayments uses the Run Merchant portal for reporting and management; Stripe uses the Stripe Dashboard
• Support model — RunPayments provides a dedicated account manager and support team for setup and ongoing assistance
• ACH format — RunPayments ACH requires routing number / account number format

Yes. RunPayments supports secure token storage similar to Stripe. When a customer pays, their card information can be tokenized for future use. Actual card numbers are never stored in TRUE — only secure tokens. Stored payment details are also accessible through the Vault in the Run Merchant portal, where you can view, edit, or charge vaulted customers.

1. Open Point of Sale and select the bank/ACH payment option
2. Click Add Bank
3. Enter the customer's banking information in the format: routing number / account number
4. Process the transaction

ACH transactions typically have lower fees than credit card payments but may take 2–3 business days to clear.

While RunPayments does not strictly require CVV and expiration date for keyed-in transactions, some card issuers may reject transactions without this information. To reduce rejections:

• Include the CVV (3 or 4 digit security code) whenever possible
• Include the expiration date if the field is available
• Double-check the card number for typos
• If all information is correct and the transaction still fails, the issue may be with the card itself (insufficient funds, expired, blocked by issuer)

If the ePay form is asking whether an account is "Checking or Savings" when a customer selects credit card payment, or if transactions are appearing as E-Check in your Run Merchant portal:

1. Verify the customer is clicking Add Card under the Credit Card option, not the Bank option
2. Check if the form is prompting for an expiration date (credit cards require this, ACH does not)
3. Review the transaction in your Run Merchant portal under Reporting > Transactions to see how it was classified
4. Contact TRUE Support if credit card entries are consistently being misrouted as E-Check

1. Do not attempt to process the transaction again immediately
2. Wait at least 2–3 minutes for the original transaction to complete or timeout
3. Log into your Run Merchant portal and check Reporting > Transactions to see if the transaction was actually processed
4. If the transaction shows as successful in the portal but not in TRUE, contact TRUE Support
5. If the transaction does not appear in the portal after 5 minutes, it is safe to retry

If a payment appears in your Run Merchant portal but isn't reflected in TRUE:

1. Refresh the TRUE window
2. Navigate away from the record and back to it
3. Check the invoice record to see if the payment is applied
4. Verify the correct customer/invoice was selected when processing
5. If the payment still doesn't appear, contact TRUE Support with the Transaction ID from the Run Merchant portal

Processing fees are visible in your Run Merchant portal:

1. Log into your Run Merchant portal
2. Navigate to Reporting > Funding
3. Click any Deposit ID to view the Funding Details, which include Net Sales, Processing Fees, and Funding Amount
4. Download monthly statements from the Statements tab for full fee breakdowns

For questions about fee structure or rate changes, contact your RunPayments account manager.

1. Log into your Run Merchant portal
2. Navigate to Reporting > Transactions
3. Click the Transaction ID of the transaction you want to refund
4. Click Reverse in the top-right corner
5. Select full refund or enter a specific amount for a partial refund

The refunded amount updates in the portal in real time, but the original transaction amount remains displayed for record keeping.

Yes. Run Merchant consolidates all of your merchant accounts and locations into one portal. Use the MID/Account filter at the top of each report to filter data by one, multiple, or all accounts. You can also create Basic user accounts that are restricted to specific MIDs for employees who only manage a single location.

Payment disputes and chargebacks are handled through the RunPayments support team:

• You will receive chargeback notifications through the Run Merchant portal
• The RunPayments support team can assist with dispute documentation and submission
• Disputes are filed directly from the Chargebacks section of the Run Merchant portal
• TRUE Support can assist with retrieving transaction details and documentation from TRUE if needed for a dispute response