Receipt Settings (Email Notifications)

Purpose:

Receipt Settings control who receives email notifications for transactions.

Location:

Navigate to Control Panel > General Settings (or Receipt Settings section)

Configuration Fields:

“Send Transaction Emails To”:

What It Does:

  • Enter email address(es) to receive notification for every successful transaction
  • Multiple emails can be entered (comma or semicolon separated)

What’s Included in Email:

  • Transaction amount
  • Customer name
  • Card type and last 4 digits
  • Authorization code
  • Date/time
  • Transaction ID
  • Link to view transaction details

Use Cases:

  • Owner wants daily sales notifications
  • Accountant monitors all revenue
  • Manager tracks all transactions
  • Sales team sees all orders

Example:

owner@company.com, accounting@company.com, manager@company.com

Volume Consideration:

  • High-volume merchants (100+ transactions/day) may want to disable this
  • Can become overwhelming
  • Consider using reports instead

“Send Transaction Error Emails To”:

What It Does:

  • Enter email address(es) to receive notification for every failed/declined/rejected transaction
  • Multiple emails can be entered

What’s Included in Email:

  • Decline reason (“Insufficient funds”, “Invalid CVV”, etc.)
  • Customer information
  • Transaction amount
  • Card last 4 digits
  • Fraud module that blocked it (if blocked by fraud)
  • Timestamp

Why This Matters:

  • Declined transactions may indicate:
    • Customer service issue (customer needs help)
    • Fraud attempt
    • Configuration problem (legitimate transactions being blocked)
    • System error

Use Cases:

  • Customer service team can proactively contact customer
  • Fraud manager monitors decline patterns
  • IT team troubleshoots integration issues
  • Operations reviews false declines

Example:

support@company.com, fraud@company.com

Disabling All Receipts:

The Problem:

  • Gateway requires an email address in these fields
  • But merchant doesn’t want receipts

The Solution:

  • Enter a fictitious email address
  • Example: noreply@fakeemail.com or donotuse@example.com
  • Emails send to nowhere
  • Merchant doesn’t receive notifications

Important: Make sure the fictitious email isn’t a real address you own, or you’ll still get notifications.

Source-Specific Receipt Emails:

Scenario:

  • Merchant wants different emails for different transaction sources:
    • Website orders → webteam@company.com
    • Hosted payment page → sales@company.com
    • Virtual terminal → office@company.com

Configuration:

  1. In Receipt Settings, enter fictitious email globally
  2. Navigate to Control Panel > Source Management
  3. Click edit icon for specific source
  4. Find “Email Merchant” field
  5. Enter source-specific email
  6. Click Save
  7. Repeat for each source

Result:

  • Virtual terminal transactions email to office@company.com
  • API transactions from website email to webteam@company.com
  • Hosted page transactions email to sales@company.com