Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| payment_werx [2025/10/28 21:37] – ftw | payment_werx [2025/10/28 21:44] (current) – ftw | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| {{ : | {{ : | ||
| - | Gateway | + | |
| - | | + | |
| - | | + | |
| - | FULL MANUAL | + | |
| - | Admin Area | + | |
| - | Admin Login Location | + | |
| - | The admin login page is located at: | + | |
| - | | + | |
| - | This page is not accessible from the public-facing site for security reasons. You must access it directly to log in as an admin. | + | |
| - | | + | |
| - | Admin accounts are stored in the tc_users database table. | + | |
| - | | + | |
| - | ● Logging in with another admin account, or | + | |
| - | ● Manually updating the password directly in the database. | + | |
| - | + | ||
| - | ADMIN | + | |
| - | User Admin Login Page | + | |
| - | Top Chart – Last 8 Months of Transactions | + | |
| - | | + | |
| - | Sales Goal | + | |
| - | This goal is based on customizable settings, which | + | |
| - | calculate your target as a percentage of monthly net | + | |
| - | revenue versus your desired net income over the past 30 | + | |
| - | days. | + | |
| - | | + | |
| - | | + | |
| - | platform. Each new purchase by a user adds them to the | + | |
| - | active user count. | + | |
| - | | + | |
| - | Shows the total gross transaction amount generated in | + | |
| - | the last 24 hours. | + | |
| - | | + | |
| - | | + | |
| - | income allocated to the admin. | + | |
| - | | + | |
| - | | + | |
| - | address) who visited the payment pages in the past 24 | + | |
| - | hours. | + | |
| - | + | ||
| - | ADMIN | + | |
| - | User Admin Dashboard | + | |
| - | Top Merchants | + | |
| - | | + | |
| - | | + | |
| - | This feature must be configured internally to display the current server load. It’s typically disabled by | + | |
| - | default due to potential performance impact but can be integrated using control panel load average | + | |
| - | reporting. | + | |
| - | My Profile | + | |
| - | Shows recent admin logins for this account, including IP addresses and login timestamps. You can | + | |
| - | also update the admin profile image by clicking Edit Profile. | + | |
| - | My Stats | + | |
| - | | + | |
| - | attempts. | + | |
| - | Top Merchants (Duplicate) | + | |
| - | Same as the "Top Merchants" | + | |
| - | | + | |
| - | | + | |
| - | edited in / | + | |
| - | User Account Setup (Merchant, Admin, or Vendor) | + | |
| - | This section allows you to create new Admin, Merchant, or Vendor accounts and manage their credentials. | + | |
| - | | + | |
| - | 1. Scroll to the bottom of the page and click “Add User” to create a new account. | + | |
| - | 2. Account Types: | + | |
| - | ○ Admin – Provides access only to the admin dashboard. You can configure specific permissions (left-side menu | + | |
| - | items). | + | |
| - | ○ Merchant – Grants access to the merchant control panel at: | + | |
| - | | + | |
| - | You can enable or disable merchant features and assign merchants to existing merchant groups. | + | |
| - | ○ Vendor – A vendor is a reseller that manages multiple merchants. Vendors can log in to /admin/ and access only | + | |
| - | the merchants or sites assigned to them. | + | |
| - | | + | |
| - | ● If using Monetra 9+, enter the Profile ID in the designated field. | + | |
| - | ● You can find available Profile IDs by clicking "See Profile IDs" on the page. | + | |
| - | + | ||
| - | ADMIN | + | |
| - | User Admin Dashboard: User Lookup / Support | + | |
| - | + | ||
| - | ● Make sure each account is connected to only one Monetra Profile ID. | + | |
| - | ● To assign the appropriate sites to a profile, use CTRL + Click in the site selection area while adding or editing the account. | + | |
| - | | + | |
| - | ● Username and Password | + | |
| - | ○ Password must be unique, with at least 7 characters, including 1 number and 1 special character (e.g., | + | |
| - | !@# | + | |
| - | ● Full Name, Email, and ZIP Code (optional) | + | |
| - | ● Profile Image (optional; can also be uploaded or edited later) | + | |
| - | | + | |
| - | ● Admin Permissions: | + | |
| - | When creating an admin, you can define which sections they can access using checkboxes for each menu item. | + | |
| - | ● Merchant Access Control: | + | |
| - | You can assign merchants to existing merchant groups. This links their login to all sites associated with that merchant. | + | |
| - | + | ||
| - | ADMIN | + | |
| - | User Admin Dashboard: User Lookup / Support | + | |
| - | + | ||
| - | ● Add/Edit Site Option: | + | |
| - | ○ If enabled, the merchant can add or modify their own sites from the /cp/ panel. | + | |
| - | ○ Recommended: | + | |
| - | | + | |
| - | ● In the User Admin panel, you can: | + | |
| - | ○ View all Admin, Merchant, and Vendor accounts | + | |
| - | ○ Activate, deactivate, or delete accounts | + | |
| - | ○ Set or adjust access permissions by account type | + | |
| - | ○ View a list of currently active users | + | |
| - | + | ||
| - | ADMIN | + | |
| - | User Admin Dashboard: User Lookup / Support | + | |
| - | + | ||
| - | Top Filters & Reporting Guide | + | |
| - | Use the top filters to customize reports based on time, users, payment status, and more. Keep in mind that all timestamps are based | + | |
| - | on the server’s timezone, which may differ from your local time unless specifically configured. | + | |
| - | Time Filters | + | |
| - | ● Quick Select: Click predefined time ranges like Last 24 Hours, Last 7 Days, etc., to instantly load reports. | + | |
| - | ● Start & End Date: Manually filter by specific year, month, or day for custom date ranges. | + | |
| - | | + | |
| - | ● By Content Partner (Merchant): View reports specific to individual merchants. | + | |
| - | ● By Site: Filter data by websites added to the platform. | + | |
| - | ● By Reseller: Show data for resellers associated with merchant accounts. | + | |
| - | Note: Resellers are not the same as vendors and typically don’t access the admin panel directly. Reports may be routed | + | |
| - | elsewhere. | + | |
| - | ● By Payment Type: Filter transactions by method (e.g., credit card, crypto). | + | |
| - | | + | |
| - | | + | |
| - | User Admin Dashboard: Reports Kount info is edited here / | + | |
| - | + | ||
| - | ● By Payment Status: | + | |
| - | ○ Complete: Transaction successfully completed by the user. | + | |
| - | ○ Incomplete: User abandoned the payment page before finishing. | + | |
| - | ○ Declined: Payment failed (e.g., insufficient funds, zip code mismatch). | + | |
| - | ○ Chargeback: Pulled from Kount, reflects a chargeback already processed. Shows as a negative amount returned to | + | |
| - | the merchant. | + | |
| - | ○ Dispute: Also from Kount; indicates a pending dispute. | + | |
| - | ■ Admins have 24 hours to alert merchants to log in to Kount to either refund or provide documentation. | + | |
| - | ■ Matching disputes with transactions may require manual order/ | + | |
| - | system can notify both the admin and merchant (if notifications are enabled). | + | |
| - | ○ Fraud Block: Indicates a transaction was blocked by Kount due to failing risk score thresholds. These are also | + | |
| - | visible to merchants. | + | |
| - | ● Other fraud-related tools include Ethoca, Verifi, RDR, and RDR Disputes — all designed for fraud detection and refund | + | |
| - | blocking. | + | |
| - | | + | |
| - | User Admin Dashboard: Reports Kount info is edited here / | + | |
| - | + | ||
| - | Card Type | + | |
| - | | + | |
| - | | + | |
| - | ● For Monetra transactions: | + | |
| - | ○ If less than 24 hours old: A Void option will be available. | + | |
| - | ○ If older than 24 hours: A Refund option will appear instead. | + | |
| - | ● For all transaction types: | + | |
| - | ○ Use Refund Reports to manually process a refund. | + | |
| - | This does not automatically process the refund through the gateway, but helps ensure consistency between your | + | |
| - | internal merchant reporting and external gateway records. | + | |
| - | | + | |
| - | | + | |
| - | User Admin Dashboard: Reports Kount info is edited here / | + | |
| - | + | ||
| - | Top Filter by Date | + | |
| - | Use the date filter at the top of the page to view reports for specific time periods such as Last 24 Hours, Last 7 Days, etc. | + | |
| - | Note: All times are based on your server' | + | |
| - | match. | + | |
| - | You can also manually select a start and end date to filter by specific day, month, or year. | + | |
| - | | + | |
| - | This report includes transactions from other installations of the platform running on separate servers (commonly referred to as black | + | |
| - | label setups). | + | |
| - | To enable cross-server reporting: | + | |
| - | ● API connections must be manually configured in the file: | + | |
| - | / | + | |
| - | ● Ensure the settings are correctly updated so your server can securely connect and receive data from the external | + | |
| - | installation. | + | |
| - | Once connected, reports from other platforms will automatically appear here — eliminating the need to log into each separate | + | |
| - | install. | + | |
| - | | + | |
| - | User Admin Dashboard: Client Reports | + | |
| - | + | ||
| - | User & Transaction Search | + | |
| - | You can search for transactions or user accounts using: | + | |
| - | ● Email Address or Account (email) | + | |
| - | ● Transaction ID, which is typically the Order ID or the Monetra TTID | + | |
| - | How to Search: | + | |
| - | 1. Enter the email or transaction ID. | + | |
| - | 2. Select a Start Date and End Date. | + | |
| - | 3. Click Submit to view results. | + | |
| - | | + | |
| - | Once submitted, you'll see the following details: | + | |
| - | ● User Information: | + | |
| - | ○ Email address | + | |
| - | ○ Account password (if stored) | + | |
| - | ○ Account creation date (how long they’ve been a user) | + | |
| - | ○ Last 4 digits of the most recently used credit card (if available) | + | |
| - | | + | |
| - | User Admin Dashboard: User Lookup | + | |
| - | + | ||
| - | ● Transaction History: | + | |
| - | ○ Date of each transaction | + | |
| - | ○ Associated site | + | |
| - | ○ Username and password (if used for a recurring transaction) | + | |
| - | ○ Description (typically the product/ | + | |
| - | ○ Expiration Date (for recurring billing, if applicable) | + | |
| - | ○ Amount | + | |
| - | ○ Status (not currently in use) | + | |
| - | | + | |
| - | ● If the transaction is processed via Monetra: | + | |
| - | ○ A Refund button will appear, allowing you to issue a refund. | + | |
| - | ● You can also select " | + | |
| - | This is useful when issuing the refund through a third-party gateway but still needing to update internal records | + | |
| - | | + | |
| - | User Admin Dashboard: User Lookup | + | |
| - | + | ||
| - | Manual Payment Link Creation | + | |
| - | Start by selecting a site from the list of sites enabled in your gateway. Then, fill in the following payment details: | + | |
| - | | + | |
| - | ● Transaction Amount: Enter a numeric value only (e.g., 49.99) | + | |
| - | ● First Name: Customer’s first name | + | |
| - | ● Last Name: Customer’s last name | + | |
| - | ● Email: Customer’s email address | + | |
| - | ● Address: Billing address | + | |
| - | ● City: Billing city | + | |
| - | ● Zip Code: Postal/ZIP code | + | |
| - | ● Country: Customer’s country | + | |
| - | ● State: Use standard abbreviations (e.g., CA, NY, TX, BC, etc.) | + | |
| - | | + | |
| - | ● Description: | + | |
| - | ● Session: This can be used to store an order ID (e.g., from WordPress) and is helpful for auto-confirmation if a postback | + | |
| - | system is enabled. | + | |
| - | | + | |
| - | User Admin Dashboard: Payment Link | + | |
| - | + | ||
| - | Optional Settings | + | |
| - | ● I will manually complete this order | + | |
| - | ○ If checked, the system will automatically mark the order as “Paid” once the payment is received. | + | |
| - | ● Redirect back to main site | + | |
| - | ○ If enabled, the user will be redirected to the main platform homepage after payment, instead of a custom return | + | |
| - | URL. | + | |
| - | After Submission | + | |
| - | Once you click Submit, you will receive: | + | |
| - | ● A QR code that you can share with the customer for payment | + | |
| - | ● A direct payment link, which can be copied to your clipboard by clicking the link icon below | + | |
| - | | + | |
| - | refresh or revisit the page and still process the payment without the usual session check safeguards. | + | |
| - | | + | |
| - | User Admin Dashboard: Payment Link | + | |
| - | + | ||
| - | Date Filter & Reconciliation Overview | + | |
| - | Use the top date filter to view reports for specific time ranges such | + | |
| - | as Last 24 Hours, Last 7 Days, etc. | + | |
| - | Note: All data is based on your server' | + | |
| - | which may differ from your local time unless configured | + | |
| - | otherwise. | + | |
| - | You can also manually set a start and end date to filter by day, | + | |
| - | month, or year. | + | |
| - | | + | |
| - | This section helps you verify and reconcile transactions processed through external platforms (e.g., a client’s WordPress site). | + | |
| - | To begin reconciliation: | + | |
| - | 1. Access the client’s transaction records — either by logging into their WordPress admin panel or requesting a CSV export | + | |
| - | of daily orders. | + | |
| - | 2. Navigate to the CSV Reconcile section in this system. | + | |
| - | 3. Upload the CSV file provided by WordPress. | + | |
| - | 4. After uploading, use this report view to identify unmatched transactions between your system and the external order | + | |
| - | data. | + | |
| - | This process ensures consistency between platform records and third-party order systems. | + | |
| - | | + | |
| - | User Admin Dashboard: Reconcile and CSV Reconcile | + | |
| - | + | ||
| - | + | ||
| - | Monetra 9+ Transaction Lookup | + | |
| - | If you're using Monetra 9+, you can verify transactions by: | + | |
| - | 1. Selecting a site from the dropdown menu. | + | |
| - | 2. Entering the TTID (Transaction ID) or Order ID in the search field. | + | |
| - | This tool is useful for confirming whether a transaction was successfully completed. | + | |
| - | | + | |
| - | User Admin Dashboard: Search by TTID | + | |
| - | + | ||
| - | Managing Sites and Merchants | + | |
| - | This section allows you to add and edit merchants and their sites within the platform. If there are many merchants, use the | + | |
| - | pagination control in the top-right corner to navigate between pages. | + | |
| - | | + | |
| - | ● Filter merchants by Active or Inactive status. | + | |
| - | ● To add a new merchant, scroll to the bottom and click Add Merchant. | + | |
| - | | + | |
| - | ● CP Name: Enter the full company or website name of the merchant. | + | |
| - | ● Merchant Percentage: Specify the percentage of revenue the merchant keeps. | + | |
| - | (For example, if you charge a 10% fee, enter 90% here.) | + | |
| - | ● Fixed Transaction Fee: Optionally enter a fixed fee amount in dollars and cents to charge per transaction. | + | |
| - | ● Email: Enter the merchant’s email address — this is where alerts like chargebacks will be sent. | + | |
| - | ● Contact Person: Provide a name of the technical contact or primary point of contact for the merchant. | + | |
| - | ● Address: Enter the merchant’s street, state, ZIP code, and country. | + | |
| - | | + | |
| - | ● You can link this merchant to a reseller (ISO) (added via the reseller section). | + | |
| - | The reseller will receive a percentage share of this merchant’s income. | + | |
| - | | + | |
| - | User Admin Dashboard: Merchant Admin | + | |
| - | + | ||
| - | | + | |
| - | ● The default currency for new sites is set in Manage Currency under the admin menu on the left. | + | |
| - | | + | |
| - | ● After adding a merchant, go to User Admin to assign login accounts for them. These accounts allow merchants to view | + | |
| - | reports and manage their sites. | + | |
| - | ● Under the merchant, you can add as many sites as needed. Sites can be edited or removed as necessary. | + | |
| - | ● You may create custom templates for each merchant if desired, though default templates are generally recommended as | + | |
| - | they require no additional development and support all billing types. | + | |
| - | ● Caution: Be careful not to accidentally delete sites. | + | |
| - | Load Balancing Settings | + | |
| - | ● In Edit Merchant (Edit CP), you can enable or disable Load Balancing. | + | |
| - | | + | |
| - | ● Assign sites to load balance between different transaction sequence numbers configured in the Edit Site pages. | + | |
| - | Fraud Prevention (Kount) | + | |
| - | ● You can enable or disable Kount fraud tools for the merchant here. | + | |
| - | ● Set default Omniscore or Personascore thresholds for all sites managed by this merchant: | + | |
| - | ○ Recommended Omniscore: 15 or less | + | |
| - | ○ Recommended Personascore: | + | |
| - | | + | |
| - | User Admin Dashboard: Merchant Admin | + | |
| - | + | ||
| - | Use the view status option to filter and view sites based on their status—active, | + | |
| - | The site name field is for internal use only and is not visible to end users. It helps identify which transactions are associated with | + | |
| - | which site and is primarily used for reporting purposes. For example: “My Site.” | + | |
| - | The description field is also internal and can be used to provide additional context about the site, such as: “My site using Elavon in | + | |
| - | Europe.” | + | |
| - | | + | |
| - | platform hosts the credit card form. | + | |
| - | The template image is a background image displayed behind the logo and payment details on the left side of the payment page. | + | |
| - | Recommended size: 500x300 pixels, PNG format. | + | |
| - | | + | |
| - | Use the template button color option to customize the color of buttons within the template (e.g., submit buttons). | + | |
| - | The contact URL is typically the link to the merchant’s contact page. | + | |
| - | The descriptor name is the business name that will appear on the customer’s bank or credit card statement. | + | |
| - | You can choose to display the site name on invoices generated and sent through the system. | + | |
| - | Token verification can be enabled to allow the use of saved cards via Auric Vault (if configured). This supports recurring billing and | + | |
| - | other future transactions. | + | |
| - | | + | |
| - | User Admin Dashboard: Merchant Admin - Edit Site | + | |
| - | + | ||
| - | The template directory (optional) allows you to set a custom folder name for templates. When accessing via SFTP, each billing | + | |
| - | provider has its own folder—such as Monetra or Elavon—and all associated site IDs should be placed within the corresponding | + | |
| - | folder (e.g., / | + | |
| - | If using OrbitalPay, enter the live credentials (not test credentials): | + | |
| - | information, | + | |
| - | When Monetra (MTRA) is enabled, you must associate a user (via User Admin) with a profile ID linked to this site. This is required | + | |
| - | when using Monetra 9 templates (templates_orbital). | + | |
| - | | + | |
| - | / | + | |
| - | If JSC is enabled for transaction processing, its configuration is also saved in the / | + | |
| - | templates_jsc. | + | |
| - | If Kalixa is enabled, it will activate the Kalixa payment system and related templates. Configuration details are stored in the | + | |
| - | / | + | |
| - | For Stripe integration, | + | |
| - | ● When using test keys, you can test with Stripe’s test cards (search " | + | |
| - | ● When using live keys, only real credit cards will work. | + | |
| - | These keys can be found in your Stripe Dashboard under the Developers section. Template folder: templates_stripe. | + | |
| - | More info: https:// | + | |
| - | | + | |
| - | User Admin Dashboard: Merchant Admin - Edit Site | + | |
| - | + | ||
| - | Enabling Clear Settle will activate the Clear Settle payment processor. Configuration settings are stored in the | + | |
| - | / | + | |
| - | If DebitWay is enabled, the DebitWay platform will be activated for this site. All settings are stored in / | + | |
| - | Template folder: templates_debitway. | + | |
| - | For DebitWay Interac / DDT, additional information such as the Website ID and Varicose Front ID must be obtained from DebitWay. | + | |
| - | More info: https:// | + | |
| - | | + | |
| - | ● Merchant login (usually the Merchant ID) | + | |
| - | ● API credentials (username and password) provided by Elavon | + | |
| - | | + | |
| - | templates_elavon. | + | |
| - | When Quickcoin is enabled, it allows the platform to receive posts from Quickcoin for mapped transactions. Any successful | + | |
| - | Quickcoin transactions will appear in reports. | + | |
| - | For First Atlantic Bank, enabling this option requires input of the Client ID and API Key. Template folder: templates_fab. | + | |
| - | | + | |
| - | ● Live API Key, API Token, SSL and Certificate file and Key file | + | |
| - | | + | |
| - | | + | |
| - | User Admin Dashboard: Merchant Admin - Edit Site | + | |
| - | + | ||
| - | NATS Enabled | + | |
| - | Your administrator will provide a NATS code to be entered into the appropriate field, along with a URL pointing to our NATS | + | |
| - | installation. Make sure to check the box to redirect directly to NATS for payment. The cascade number and biller name will also be | + | |
| - | supplied by the administrator. This setup redirects users to a NATS-hosted payment page and then returns them to the platform. One | + | |
| - | NATS code is hardcoded to our hosted NATS postbacks for a single site URL — please provide us with the necessary URLs so we | + | |
| - | can assign the correct site IDs. Refer to the last page of this manual for a list of billing companies compatible with NATS. | + | |
| - | | + | |
| - | You will need to enter your Merchant ID, password, merchant name, country code, email, phone number, legal name, and trading | + | |
| - | name. This configuration is based on the integration of the Mastercard Direct Gateway. For hosted payments, Mastercard will host the | + | |
| - | card input page. For non-hosted payments, the platform will host the card page using templates from the templates_mastercard | + | |
| - | folder. See the integration section at the end of this document for details. | + | |
| - | Stick Enabled (STICKY) | + | |
| - | Your administrator will provide a Sticky code to be entered into the NATS code field. This is a third-party add-on platform. A list of all | + | |
| - | compatible gateways can be found at the end of this document. We will provide an instance of this platform for an additional fee, | + | |
| - | along with the required field information to host the payment page. This page will support all gateways available through the Sticky | + | |
| - | platform. Each biller integration is configured within this third-party system. | + | |
| - | | + | |
| - | | + | |
| - | through Interac via our integration partner. | + | |
| - | | + | |
| - | User Admin Dashboard: Merchant Admin - Edit Site | + | |
| - | + | ||
| - | Square Enabled | + | |
| - | To enable Square, provide your Access Token, Account ID, and Location ID. Detailed instructions on where to enter these fields can | + | |
| - | be found at the bottom of this document. The integration can either be hosted locally on the platform using the templates_square | + | |
| - | folder or redirected to Square’s own hosted payment pages. You can toggle between sandbox and production modes as needed. | + | |
| - | | + | |
| - | Adds Payroc as a payment gateway option. Refer to the end of this document for integration steps. You can configure it for sandbox | + | |
| - | or production environments. Payments can be processed through a self-hosted page (using templates_payroc) or redirected to | + | |
| - | Payroc’s own gateway. To set this up, you will need to provide your API Key, API Secret, and Terminal ID. | + | |
| - | Nuvei Enabled | + | |
| - | Adds the Nuvei integration payment gateway option. Refer to the end of this document for integration details. You can configure it to | + | |
| - | operate in sandbox or production mode. The payment page can be self-hosted on the platform using the templates_payroc folder | + | |
| - | or redirected to Nuvei’s hosted gateway. To set this up, you will need to provide your Merchant ID, Merchant Site ID, and Secret Key. | + | |
| - | Save Credit Card | + | |
| - | | + | |
| - | the user’s complete card number and should be avoided for security reasons. | + | |
| - | Auric Vault Enabled | + | |
| - | When enabled, Auric Vault will tokenize the card information whenever a transaction is made. This token can then be used for future | + | |
| - | transactions such as rebills, improving security by avoiding storing full card data. | + | |
| - | Host Payment Page | + | |
| - | | + | |
| - | | + | |
| - | User Admin Dashboard: Merchant Admin - Edit Site | + | |
| - | + | ||
| - | Enable ID Check | + | |
| - | When enabled, this turns on Persona ID Verification or other integrated identity verification services. It triggers a popup if the user’s | + | |
| - | email address is not already verified in the database. Once verified, the popup will not appear on subsequent visits to the transaction | + | |
| - | page. | + | |
| - | " | + | |
| - | Max Amount Allowed | + | |
| - | This sets the maximum amount a user can spend per transaction on the purchase page. If a user tries to purchase more than this | + | |
| - | limit, the transaction will be blocked with a message indicating the limit has been exceeded. For example, if the max is set to 500 and | + | |
| - | the user tries to purchase 501, the transaction will be rejected. | + | |
| - | | + | |
| - | This is the maximum total amount allowed in transactions on the site within a rolling 24-hour period. Once this daily limit is reached, | + | |
| - | the merchant is notified, and users see a message stating the maximum amount of transactions for the day has been reached. These | + | |
| - | limits can be adjusted or removed at any time. | + | |
| - | | + | |
| - | This is used for load balancing based on transaction amounts or counts. For example, if the site is set to sequence number 3, it will | + | |
| - | process transactions after sites 1 and 2 have completed theirs. Make sure to enable this setting on the merchant edit page as well; | + | |
| - | otherwise, it will not function. | + | |
| - | | + | |
| - | | + | |
| - | commission based on the merchant’s sales. | + | |
| - | | + | |
| - | User Admin Dashboard: Merchant Admin - Edit Site | + | |
| - | + | ||
| - | Referral Domain | + | |
| - | When enabled, only sites matching the specified domain are allowed to process transactions for this site ID. This helps prevent | + | |
| - | unauthorized use of the site ID through shared links or plugins. | + | |
| - | Main URL | + | |
| - | Enter the full URL of the site, including the trailing slash. | + | |
| - | | + | |
| - | Used when rebilling is active, this URL directs users to the member login area after completing a transaction, | + | |
| - | site.com/ | + | |
| - | | + | |
| - | Used for sites that offer both free and paid content, this URL points to the free preview or tour area, such as tour.mysite.com. | + | |
| - | | + | |
| - | This is the URL where the postback script is located. Typically, in WordPress setups, it might be found under | + | |
| - | / | + | |
| - | send postback and return URLs during integrations (e.g., pb=http:// | + | |
| - | to_complete=https:// | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | This URL receives a delayed postback, typically sent about 10 seconds after the first postback as a confirmation or fallback in case | + | |
| - | the initial postback failed. The system ensures the data matches the first postback to maintain consistency. | + | |
| - | | + | |
| - | User Admin Dashboard: Merchant Admin - Edit Site | + | |
| - | + | ||
| - | Percentage | + | |
| - | If checked, the commission percentage will match what is set for the merchant. If unchecked, you can specify a custom percentage to | + | |
| - | give the merchant (e.g., if the merchant receives 90%, you enter 90%). | + | |
| - | Fixed Amount Fee | + | |
| - | If checked, the fee will match the amount set in the merchant edit page. If unchecked, you can specify a custom fixed fee here. | + | |
| - | | + | |
| - | When enabled, this allows API data to be sent to the merchant through another system, such as a mobile app card form, using JSON | + | |
| - | request calls. In this setup, the card page is no longer hosted on the platform but posts directly to it. Currently, this feature works only | + | |
| - | with Monetra 9+. You can also configure the maximum transaction amount allowed via API and specify IP addresses permitted to send | + | |
| - | API calls. Card details like number and name can be sent via the API. The API endpoint is located in /api/. | + | |
| - | | + | |
| - | This feature is no longer in use. It was originally designed to detect mobile devices before all templates became fully responsive. | + | |
| - | | + | |
| - | If you prefer not to enable Kount at the merchant level for all sites, you can activate it here specifically for this site. You can also toggle | + | |
| - | Kount fraud tools on or off. When enabled, you can set default fraud scores—Omniscore or Personascore—for all sites managed by | + | |
| - | this merchant. Recommended thresholds are 15 or less for Omniscore and 70+ for Personascore. These settings override any scores | + | |
| - | set in the merchant edit page. | + | |
| - | | + | |
| - | User Admin Dashboard: Merchant Admin - Edit Site | + | |
| - | + | ||
| - | Manage Customer Levels | + | |
| - | This feature tracks the transaction history of users by monitoring how many transactions they have completed. For WordPress, this | + | |
| - | happens automatically within the plugin. For custom API integrations, | + | |
| - | indicating the user’s total transactions. Based on transaction counts, users can be categorized into levels such as Basic, Standard, | + | |
| - | and VIP. For example: | + | |
| - | ● Basic: 0–5 transactions | + | |
| - | ● Standard: 6–10 transactions | + | |
| - | ● VIP: 50 or more transactions | + | |
| - | These levels are tracked using the user’s email address. | + | |
| - | | + | |
| - | Based on the assigned customer levels, transaction limits can be set for different time periods. For instance, a Basic user might be | + | |
| - | limited to 5 transactions per 30 days, a Standard user to 10 per 30 days, and a VIP user to 50 per 30 days. | + | |
| - | | + | |
| - | | + | |
| - | and is determined solely by the user’s historical transaction amounts. For example, if a user has transacted $5,000 in total, they might | + | |
| - | be allowed to complete up to 30 transactions per day. | + | |
| - | | + | |
| - | The currency options available are based on the currencies configured in the admin under Manage Currencies. These currencies are | + | |
| - | not automatically converted, but conversion can be done using an external API. You can add more currencies through the Manage | + | |
| - | Currencies section located in the bottom left menu of the admin panel. | + | |
| - | | + | |
| - | User Admin Dashboard: Merchant Admin - Edit Site | + | |
| - | + | ||
| - | Alternative Currencies | + | |
| - | When enabled, this feature shows additional currencies as a dropdown in the payment templates. For instance, a user might see a | + | |
| - | payment amount of $10 USD along with the equivalent amount displayed in another currency as a reference. | + | |
| - | | + | |
| - | You can enable credit card payment options and configure them under the Manage Cards section in the bottom left menu. This includes | + | |
| - | uploading logos and enabling or disabling various card types. When the platform hosts the card page, these logos will be displayed to | + | |
| - | users, showing them the available payment options. | + | |
| - | | + | |
| - | | + | |
| - | ACH Charge Settings | + | |
| - | Below the ACH toggle, you can customize ACH charge settings if you do not want to use the merchant’s default percentage. Options | + | |
| - | such as Directpay and EU ACH can also be enabled here. | + | |
| - | | + | |
| - | When enabled, this collects additional customer information beyond the card details, such as first and last name, address, and other | + | |
| - | personal data, if provided. | + | |
| - | | + | |
| - | This option, available only with Orbital Pay, allows you to enable multiple merchant accounts and automatically switch between them | + | |
| - | based on priority (1, 2, 3, 4, etc.). This differs from load balancing, as it cycles through merchant accounts for Orbital Pay specifically. | + | |
| - | | + | |
| - | If Orbital Pay is enabled, you can add subscription, | + | |
| - | (e.g., pay $10 for 30 days), and the payment will automatically recur according to the amount and period set. | + | |
| - | | + | |
| - | User Admin Dashboard: Merchant Admin - Edit Site | + | |
| - | + | ||
| - | Load Balancing Options: Per Amount and Per Transaction | + | |
| - | ● Per Amount: | + | |
| - | Use this option to distribute transactions across multiple processors based on a dollar limit. Each processor will accept | + | |
| - | transactions up to the set threshold; once reached, new transactions will be routed to the next available processor. | + | |
| - | ● Per Transaction: | + | |
| - | This option alternates the transaction flow between processors with every new transaction, | + | |
| - | them. | + | |
| - | | + | |
| - | User Admin Dashboard: Load Balancing | + | |
| - | + | ||
| - | + | ||
| - | Add / Edit ISO (Reseller) | + | |
| - | ● To add a new ISO (also known as a reseller), click Add ISO, enter the full company name and email address, then submit. | + | |
| - | ● You can edit or delete existing ISOs as needed. | + | |
| - | | + | |
| - | ● After adding an ISO, you’ll find an ISO dropdown on the Site Edit pages. Use this to assign individual sites to the selected | + | |
| - | ISO. | + | |
| - | ● Alternatively, | + | |
| - | ISO Compensation | + | |
| - | ● The system does not automatically calculate or distribute commission percentages for ISOs. | + | |
| - | ● You simply assign ISOs to sites and provide them with reports showing their connected sites. | + | |
| - | ● Payments to ISOs should be made manually based on your agreed-upon commission percentage. | + | |
| - | | + | |
| - | User Admin Dashboard: ISO Admin | + | |
| - | + | ||
| - | Email Templates | + | |
| - | In this section, you can add new email templates tailored to various platform functions or edit existing templates. You can also | + | |
| - | remove templates or copy them to another installation for reuse. | + | |
| - | For example, you might copy a specific email template to another site to maintain consistency across platforms. | + | |
| - | | + | |
| - | ● New user account registration | + | |
| - | ● Purchase receipt confirmation | + | |
| - | | + | |
| - | Many of these email functions are often disabled because merchants typically send their own emails, or the payment gateway | + | |
| - | handles it directly (e.g., Stripe sending invoices to customers). | + | |
| - | | + | |
| - | ADMIN | + | |
| - | User Admin Dashboard: Email Admin | + | |
| - | + | ||
| - | Manage User Accounts | + | |
| - | Here, you can search for users by their email address and edit their account details. | + | |
| - | You can view the account creation date and see whether the user is currently active or inactive. | + | |
| - | | + | |
| - | | + | |
| - | User Admin Dashboard: Account Admin | + | |
| - | + | ||
| - | ID Verification (IDV) Using Inverite or Persona or Similar Third-Party Services | + | |
| - | ID Verification can be enabled on the merchant’s site, allowing you to view all users who have successfully completed IDV. | + | |
| - | ● This feature is activated via the Site Edit page by toggling the IDV enabled option. | + | |
| - | ● When enabled, users without verified IDs will see a popup prompting them to complete verification if their email is not yet | + | |
| - | approved. | + | |
| - | Batch Import and Approval | + | |
| - | You can also bulk import users and approve multiple accounts at once using the upload and approve function. | + | |
| - | | + | |
| - | User Search and Management | + | |
| - | | + | |
| - | From here, you can manually approve users, delete them, or add them to a blacklist. | + | |
| - | | + | |
| - | User Admin Dashboard: IDV Users | + | |
| - | + | ||
| - | Electracash ACH (or Similar ACH) Check Processing | + | |
| - | If enabled, you can manage ACH check payments processed through Electracash or a similar service. | + | |
| - | ● View checks that have cleared and manually mark them as approved. | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | User Admin Dashboard: Pending Checks | + | |
| - | + | ||
| - | Deposit Payment Option | + | |
| - | If the deposit payment option is enabled, customers can pay with cash, credit card, or biller at a physical location. | + | |
| - | | + | |
| - | You can manually complete pending or made transactions by searching with the following filters: | + | |
| - | ● Date range (Today, Yesterday, Last 3 days, This month, Last month, Last 2 months, This year) | + | |
| - | ● Amount | + | |
| - | ● Invoice # / Order # / DEP# / Session ID | + | |
| - | ● Description or email | + | |
| - | | + | |
| - | ● Pending: Transaction recorded but not yet completed by the customer. | + | |
| - | ● Canceled: Transaction canceled by admin or customer. | + | |
| - | ● Complete: Transaction marked paid here or confirmed via an integrated API from the payment location. | + | |
| - | ● Expired: Transactions automatically expire after 2 days. | + | |
| - | | + | |
| - | User Admin Dashboard: Deposits | + | |
| - | Additional Filters | + | |
| - | ● Location: Select deposit locations configured on the Deposits Accounts page. | + | |
| - | | + | |
| - | Site: Filter by sites that have deposit payments enabled (set on the Edit Site page). | + | |
| - | | + | |
| - | Click Create New Location Deposit to manually generate a pending transaction, | + | |
| - | payment link. You can then approve it manually. | + | |
| - | Load Balancing | + | |
| - | The deposit system supports automatic load balancing, cycling through locations in rotation to distribute | + | |
| - | transactions evenly. | + | |
| - | | + | |
| - | User Admin Dashboard: Deposits | + | |
| - | Manage Deposit Accounts | + | |
| - | Here, you can edit or delete any active deposit accounts that have been added to the platform. | + | |
| - | These accounts typically represent physical locations where customers can make payments | + | |
| - | either in person with cash or by card, similar to using a payment link. | + | |
| - | You can view the sites connected to each location, along with their assigned site IDs, account | + | |
| - | numbers, and location IDs. | + | |
| - | These unique identifiers help ensure customers are paying to the correct location and address. | + | |
| - | | + | |
| - | User Admin Dashboard: Deposit Accounts | + | |
| - | + | ||
| - | Deposit Transactions and Reconciliation | + | |
| - | If the deposit system is enabled, you can view transactions that have automatically cleared and manually clear any that have | + | |
| - | not. You can also review unmatched deposit transactions. | + | |
| - | In the Configuration section (button at the top right), you can manage enabled deposit automation locations and toggle | + | |
| - | automatic reconciliation on or off. | + | |
| - | Date Filters | + | |
| - | ● Today | Yesterday | Last 3 days | This month | Last month | Last 2 months | This year | + | |
| - | ● Start Date: The date when the pending transaction was created | + | |
| - | ● End Date: The last date within your chosen filter range | + | |
| - | | + | |
| - | ● Next Update: Displays when the next cron job will run to automatically update transactions on this page. | + | |
| - | | + | |
| - | ● Transaction Amount: Search by the dollar amount of completed or pending transactions | + | |
| - | ● Deposit Location: Filter by active deposit locations using the dropdown | + | |
| - | ● Content Partner: Filter by the associated merchant | + | |
| - | ● Site: Filter by sites where deposits are enabled | + | |
| - | | + | |
| - | User Admin Dashboard: Deposit Transactions | + | |
| - | + | ||
| - | Manage Payouts | + | |
| - | Set payouts by date range and on a per-site basis. You can create new payouts, view them here, mark them as paid, or filter by | + | |
| - | status—defaulting to pending payouts. | + | |
| - | | + | |
| - | Click the Create New Payout button to select a site and view all transactions (including test transactions if desired) for that site. | + | |
| - | Then, generate a payout request. | + | |
| - | You can specify: | + | |
| - | ● The payout fee | + | |
| - | ● Additional fees based on transaction | + | |
| - | volume within a defined range (e.g., an | + | |
| - | extra fee for every transaction beyond 100) | + | |
| - | ● Minimum and maximum transaction | + | |
| - | amounts for fee application | + | |
| - | ● Notes for reference | + | |
| - | Once created, the payout will be listed as pending and can be sent to the merchant as a PDF. | + | |
| - | | + | |
| - | User Admin Dashboard: Payout | + | |
| - | + | ||
| - | Fee and Rate Descriptions | + | |
| - | ● Decline Recapture Rate (%): Fee charged for successfully recapturing declined transactions. | + | |
| - | ● Completed Fee: Individual transaction fee paid by the merchant, added to their invoice. | + | |
| - | ● Incomplete Fee: Fee applied to incomplete transactions. | + | |
| - | ● Per Decline Fee: Fee charged for each declined transaction, | + | |
| - | attempts. | + | |
| - | ● Per Dispute Fee: Fee for disputed transactions, | + | |
| - | chargebacks. | + | |
| - | ● Fraud Block Fee: Charged when a user is blocked by Kount during a transaction attempt. | + | |
| - | ● Fraud Check Fee: Fee for users approved by Kount after a fraud check during a transaction. | + | |
| - | ● Ethoca Dispute Fee: Fee associated with disputes handled by Ethoca. | + | |
| - | ● Verifi Dispute Fee: Fee for disputes processed by Verifi. | + | |
| - | ● RDR Alerts & Disputes Fees: Fees for dispute and alert handling by RDR. | + | |
| - | ● ID Verified Fee: Charged when an ID verification check is performed against the existing database. | + | |
| - | ● New ID Validated Fee: Fee for verifying a new ID through Persona or other third-party services. | + | |
| - | ● Refund Fee: Fee applied for refunds processed either automatically or manually through the platform or | + | |
| - | gateway. | + | |
| - | ● Customer Service Amount (Hourly): Hourly fee charged for customer support provided to merchants. | + | |
| - | ● GST (%): Goods and Services Tax applicable in countries like Canada and Australia. | + | |
| - | ● PST (%): Provincial Sales Tax used in Canada or some US regions. Only one tax percentage should be | + | |
| - | applied if using a single tax type; otherwise, other tax types will not appear on invoices. | + | |
| - | | + | |
| - | User Admin Dashboard: Default Invoice Fees | + | |
| - | + | ||
| - | Create a Custom Invoice for Merchant | + | |
| - | This feature allows you to generate detailed, customizable PDF invoices for merchants, which can be sent manually and | + | |
| - | tracked in the invoice list. You can include transaction fees, security deposits, chargebacks, | + | |
| - | Invoices can be created based on a specific site and date range. | + | |
| - | How it works: | + | |
| - | ● At the top, select the desired date range and choose either a merchant or site for the invoice. | + | |
| - | ● The system will then display key figures including: | + | |
| - | ○ Total (Complete): Number of completed transactions | + | |
| - | ○ Total (Incomplete): | + | |
| - | ○ Chargebacks: | + | |
| - | ○ Fraud Check Complete: Users who passed Kount’s fraud check during transactions | + | |
| - | ○ Disputes: Chargebacks in progress—typically requiring a response within 24 hours to dispute or refund | + | |
| - | ○ New ID Validated Complete: New users added to the ID verification database via Kount | + | |
| - | ○ ID Verified: Current user ID verification status | + | |
| - | ○ Fraud Checked Incomplete: Users blocked by Kount during transactions | + | |
| - | ○ New ID Checked Incomplete: Users who left the transaction page but were still checked by Kount | + | |
| - | ○ Total Transactions (Complete/ | + | |
| - | | + | |
| - | | + | |
| - | User Admin Dashboard: Create Invoice | + | |
| - | + | ||
| - | Edit or delete any custom invoices created by the admin for merchants. | + | |
| - | | + | |
| - | receives the correct data. | + | |
| - | You can download the invoice, mark it as paid, or make edits as needed. | + | |
| - | | + | |
| - | User Admin Dashboard: List Invoices | + | |
| - | + | ||
| - | Blacklist | + | |
| - | | + | |
| - | You can also remove (clear) users or IPs from the blacklist if needed. | + | |
| - | In the future, bulk imports from the MySQL table tc_blacklist may be supported to add multiple entries | + | |
| - | at once. | + | |
| - | Users on this list will be blocked from transacting on any payment pages. | + | |
| - | | + | |
| - | User Admin Dashboard: Blacklist | + | |
| - | + | ||
| - | Reset failed login attempts for admin or merchant control panel (/cp) logins. | + | |
| - | This section shows failed login attempts by users. You can reset them to | + | |
| - | unblock accounts or IPs that have been temporarily blocked. | + | |
| - | | + | |
| - | User Admin Dashboard: IP Block and Unblock | + | |
| - | + | ||
| - | Multi-Language Template Support | + | |
| - | If the template supports multiple languages, you can select or add new languages here. Customize the | + | |
| - | translation of any front-end text—like “submit”—to your preferred language. | + | |
| - | Note: Translations are initially done using Google Translate and may need manual edits using the translate | + | |
| - | button for accuracy. | + | |
| - | To add a new language, import it into the tc_languages database table. | + | |
| - | | + | |
| - | User Admin Dashboard: Manage Language | + | |
| - | + | ||
| - | Add and Manage Currencies | + | |
| - | Add currencies to display on the front-end templates and payment options. | + | |
| - | Set the default currency, which serves as the base for all others. You can add multiple currencies, but you’ll | + | |
| - | need to manually enter the exchange rates (e.g., 1 USD = 0.75 EUR). | + | |
| - | | + | |
| - | Make sure the gateway’s default currency matches one of the currencies you’ve added to ensure proper | + | |
| - | processing. | + | |
| - | | + | |
| - | User Admin Dashboard: Manage Currency | + | |
| - | + | ||
| - | Manage Payment Card Options | + | |
| - | Add or remove different payment card logos that appear on the front-end templates. | + | |
| - | These logos serve as a visual guide to show users which payment methods are available, but they do not | + | |
| - | control or manage the actual payment options. | + | |
| - | The payment gateway is responsible for determining which payment types are accepted. | + | |
| - | | + | |
| - | User Admin Dashboard: Manage Credit Cards | + | |
| - | + | ||
| - | ADMIN | + | |
| - | User Admin Dashboard: E-Wallet Configuration Values | + | |
| - | + | ||
| - | Load Fee: Example values—$1.00 (fixed) or 20% (percentage). This fee is charged by the platform admin each time a | + | |
| - | customer loads money into their E-wallet via the /myaccount section. | + | |
| - | | + | |
| - | from their E-wallet in the /myaccount section. Also known as a customer payout. | + | |
| - | | + | |
| - | E-wallet user within the /myaccount section. | + | |
| - | ACH Load Fee: Example values—$1.00 (fixed) or 20% (percentage). Fee applied when a customer loads money into their | + | |
| - | E-wallet using an ACH gateway in the /myaccount section. | + | |
| - | ACH Withdrawal Fee: Example values—$1.00 (fixed) or 20% (percentage). Charged when a customer withdraws money from | + | |
| - | their E-wallet via an ACH gateway. | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | verified. | + | |
| - | | + | |
| - | verified. | + | |
| - | | + | |
| - | verification. | + | |
| - | | + | |
| - | verification. Redirect is useful when popups are blocked by some platforms. | + | |
| - | | + | |
| - | | + | |
| - | NATS, Square, Sticky, Payroc, Elavon). Multiple can be active simultaneously. Currently, only Stripe supports payouts. | + | |
| - | E-Wallet Add-on: | + | |
| - | If the E-Wallet feature is enabled, please note that you must hold a valid Money Service Business license | + | |
| - | in the country, state, province, or district where you operate this service. | + | |
| - | | + | |
| - | | + | |
| - | sets daily limits for transferring, | + | |
| - | Customers can request to upgrade or downgrade their daily limits, and all requests require admin approval | + | |
| - | via the E-Wallet Upgrade Requests page. | + | |
| - | | + | |
| - | When customers request a change in their daily transfer limits from the available account levels, an email | + | |
| - | notification is sent to the main admin email specified in the platform’s tc_config file. The admin can then | + | |
| - | review and approve or deny these requests on the E-Wallet Upgrade Requests page. | + | |
| - | | + | |
| - | If enabled on the payment page via the E-Wallet configuration settings, customers may use their E-Wallet | + | |
| - | balance to complete payments directly from their account balance. | + | |
| - | | + | |
| - | User Admin Dashboard: Manage E-Wallet Upgrade Requests | + | |
| - | and Account Levels | + | |
| - | + | ||
| - | + | ||
| - | Gateway | + | |
| - | | + | |
| - | | + | |
| - | FULL MANUAL | + | |
| - | CP (MERCHANT) Area | + | |
| - | Access the Control Panel: | + | |
| - | The control panel for merchants (CP) is located at yourinstalldomain.com/ | + | |
| - | You must use this URL to log in as a CP or merchant, as this page is not accessible | + | |
| - | from the front-end for security reasons. | + | |
| - | User accounts for CP and merchants are managed in the tc_users database table. | + | |
| - | Password resets can be done either by logging in with another account that has the | + | |
| - | necessary permissions or by updating the password directly in the database. | + | |
| - | + | ||
| - | ADMIN | + | |
| - | User CP Login Page | + | |
| - | View transactions from the past 8 months in the top chart. | + | |
| - | Sales Goal is based on settings that compare the desired | + | |
| - | net income percentage to actual monthly net revenue over | + | |
| - | the last 30 days. This can be adjusted as needed. | + | |
| - | | + | |
| - | currently on the platform. Each new purchase adds a new | + | |
| - | active user. | + | |
| - | | + | |
| - | processed in the last 24 hours. | + | |
| - | | + | |
| - | gross income earned by the admin from merchants. | + | |
| - | | + | |
| - | payment pages, tracked by IP address. | + | |
| - | + | ||
| - | CP | + | |
| - | CP Dashboard | + | |
| - | My Profile: Displays the last login dates and IP addresses for this admin account. | + | |
| - | You can also update the admin’s profile image by clicking on “Edit Profile.” | + | |
| - | My Stats: Shows the total number of successful logins and failed login attempts for | + | |
| - | this admin account. | + | |
| - | Top Merchants: Same as the top merchants section displayed elsewhere. | + | |
| - | | + | |
| - | which can be edited in / | + | |
| - | CP | + | |
| - | CP / Merchant Dashboard: My Reports | + | |
| - | + | ||
| - | Top Date Filter: | + | |
| - | Click on any time period (e.g., Last 24 hours) to view the reports below. Note that the times are based on your server’s timezone, | + | |
| - | which may differ from your local timezone unless specifically matched. | + | |
| - | Start and End Date: | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | ● Complete: Transaction was successfully completed by the user. | + | |
| - | ● Incomplete: User left the payment page before finishing the transaction. | + | |
| - | ● Declined: Credit card payment failed due to reasons like insufficient funds, zip mismatch, etc. | + | |
| - | ● Chargeback: A confirmed chargeback reported by Kount, reflected as a negative amount to the merchant. Kount retrieves | + | |
| - | daily chargeback reports via gateway login and posts them here. | + | |
| - | ● Dispute: A potential chargeback flagged by Kount. The admin has 24 hours to notify the merchant, who must log into Kount | + | |
| - | to either refund the transaction or upload proof validating it. Since Kount may not provide matching order IDs, the admin must | + | |
| - | cross-reference the transaction via the merchant’s gateway using session or order IDs, then associate and notify the | + | |
| - | merchant and admin accordingly if enabled. | + | |
| - | ● Fraud Block: Triggered by Kount when a user’s fraud score is too low or high, blocking the transaction and returning the | + | |
| - | user to the merchant’s site. Merchants will also see this status. | + | |
| - | CP | + | |
| - | CP / Merchant Dashboard: My Reports | + | |
| - | + | ||
| - | Card Type: | + | |
| - | | + | |
| - | Void and Refund Options: | + | |
| - | ● For Monetra transactions under 24 hours old, a Void option is available. | + | |
| - | ● Transactions older than 24 hours show a Refund option. | + | |
| - | ● For all transaction types, you can click Refund Reports to initiate a manual refund process. The | + | |
| - | admin can then perform the refund directly through the relevant gateway (Stripe, etc.) to ensure | + | |
| - | merchant reports align with gateway records. | + | |
| - | CP | + | |
| - | CP / Merchant Dashboard: Refund Requests | + | |
| - | | + | |
| - | where merchants submit transaction details for refund requests, which will then be emailed to the admin for | + | |
| - | manual processing. | + | |
| - | For Monetra users, there is an option to enable merchants to perform their own refunds and voids directly. | + | |
| - | This feature can be activated in the My Reports section but is currently disabled. | + | |
| - | CP | + | |
| - | CP / Merchant Dashboard: Testing Bed | + | |
| - | + | ||
| - | Merchants can send messages to you through this form. You can edit the existing form or create a new one | + | |
| - | where merchants submit transaction details for refund requests, which will then be emailed to the admin for | + | |
| - | manual processing. | + | |
| - | For Monetra users, there is an option to enable merchants to perform their own refunds and voids directly. | + | |
| - | This feature can be activated in the My Reports section but is currently disabled. | + | |
| - | CP | + | |
| - | CP / Merchant Dashboard: Payouts | + | |
| - | + | ||
| - | If the admin has created a payout request, it will appear here for the merchant. This is typically used when | + | |
| - | the admin manages a third-party payment processor, collecting all funds through their own merchant | + | |
| - | account and then releasing payments to individual merchants. | + | |
| - | | + | |
| - | the merchant admin settings. | + | |
| - | CP | + | |
| - | CP / Merchant Dashboard: Search by Ttid | + | |
| - | + | ||
| - | Here, a merchant can search for a transaction using the transaction ID. | + | |
| - | This feature is primarily for Monetra transactions but may also support searching by order ID or other | + | |
| - | biller-specific transaction IDs. | + | |
| - | The search results will display details such as the amount, date, user email, and more. | + | |
| - | CP | + | |
| - | CP / Merchant Dashboard: Lookup users | + | |
| - | + | ||
| - | Merchants can search for users who have made transactions on their sites by email or transaction ID, and | + | |
| - | filter results by a start and end date. | + | |
| - | Similar to the admin view, this displays the user’s email, account creation date, and their past transactions. | + | |
| - | Merchants can also initiate refund requests, which redirect them to the refund page. | + | |
| - | ID Verification (IDV) using Inverite, Persona or similar third-party services | + | |
| - | You can enable ID Verification at the merchant site level. Once enabled, this section displays all users who | + | |
| - | have successfully completed IDV. | + | |
| - | This feature is toggled on or off in the site edit page under the "IDV enabled" | + | |
| - | prompts users whose email is not yet verified to complete the ID verification process. | + | |
| - | You can also bulk import new users and approve multiple users at once using the upload and approve | + | |
| - | function—just ensure the CSV file follows the provided instructions. | + | |
| - | | + | |
| - | you to manually approve users, delete them, or add them to a blacklist as needed. | + | |
| - | CP | + | |
| - | CP / Merchant Dashboard: IDV Users | + | |
| - | + | ||
| - | Merchant Payment Preference Form | + | |
| - | This form allows merchants to specify their preferred payment method. | + | |
| - | If you are holding funds on behalf of a merchant, they can use this form to request how they would like to | + | |
| - | receive their payments—whether via checking account, wire transfer, or other options. | + | |
| - | | + | |
| - | CP | + | |
| - | CP / Merchant Dashboard: Payment Information | + | |
| - | + | ||
| - | Merchants can view their outstanding invoices here. | + | |
| - | Each invoice is dated and clearly marked as paid or pending payment. Merchants can also download invoices | + | |
| - | as PDFs. | + | |
| - | The invoice reflects the total gross amount owed for a specific pay period and site, based on the value set by | + | |
| - | the admin. | + | |
| - | CP | + | |
| - | CP / Merchant Dashboard: Invoices | + | |
| - | + | ||
| - | Upload files here to assist with reconciliation, | + | |
| - | transactions. | + | |
| - | | + | |
| - | only supports WordPress sites. | + | |
| - | | + | |
| - | highlight any unmatched transactions for manual review. This is especially useful when postbacks | + | |
| - | occasionally fail. | + | |
| - | CP | + | |
| - | CP / Merchant Dashboard: Reconciliation | + | |
| - | + | ||
| - | Select a site assigned to the merchant’s account and enter the following details: | + | |
| - | ● Transaction Amount: Must be a numeric value | + | |
| - | ● First Name: Customer’s first name | + | |
| - | ● Last Name: Customer’s last name | + | |
| - | ● Email: Customer’s email address | + | |
| - | ● Address: Customer’s address | + | |
| - | ● City: Customer’s city | + | |
| - | ● Zip Code: Customer’s postal code | + | |
| - | ● Country: Customer’s country | + | |
| - | ● State: Customer’s state or province (e.g., CA, AL, AK, BC) | + | |
| - | ● Description: | + | |
| - | ● Session: This can be the WordPress order ID if you want the payment to auto-complete via postback, typically the same | + | |
| - | as the order ID | + | |
| - | | + | |
| - | ● I will manually complete this order: If checked, the merchant will automatically mark this item as paid once payment is | + | |
| - | made. | + | |
| - | ● Redirect back to main site: If enabled, users will be redirected to the main platform page after payment instead of the URL | + | |
| - | set here. | + | |
| - | After submitting, you can copy the QR code to send to the customer or click the icon below to copy the payment link to your | + | |
| - | clipboard. | + | |
| - | payments without that check. | + | |
| - | CP | + | |
| - | CP / Merchant Dashboard: Payment Link | + | |
| - | + | ||
| - | Gateway | + | |
| - | | + | |
| - | | + | |
| - | FULL MANUAL | + | |
| - | CP (My Account) (Customer Area) | + | |
| - | This optional section allows customers to log in or create an account to make payments or load their e-wallet, if enabled. To | + | |
| - | create an account, customers simply provide basic information such as their email, password, and first and last name. | + | |
| - | | + | |
| - | Password” option, which will prompt a popup to enter their email and receive a new password. | + | |
| - | | + | |
| - | My Account Dashboard: Login / Add Account | + | |
| - | + | ||
| - | Once logged in, customers can access their account dashboard, where they can: | + | |
| - | Edit their profile: | + | |
| - | Load funds (if the e-wallet system is enabled) | + | |
| - | View their membership duration, Update their saved payment card, My Account Features | + | |
| - | | + | |
| - | Edit Profile: Takes the customer to the profile edit page where they can update their email address and other details. | + | |
| - | | + | |
| - | directs them to a page where they can deposit funds using any of the biller types configured by the admin under | + | |
| - | deposits. | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | My Account Dashboard: Home | + | |
| - | + | ||
| - | + | ||
| - | My Active Subscriptions | + | |
| - | This section lists any active subscriptions the customer has, showing the following details: | + | |
| - | Site Description Username Password Expiration DateStatus Action | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Shows a record of all purchases and subscriptions, | + | |
| - | Date Site Description Amount Fee Pay Type Username Password Status | + | |
| - | Pay Type: “C” indicates credit card payments, “D” indicates deposits made at a location. | + | |
| - | | + | |
| - | | + | |
| - | My Account Dashboard: Home | + | |
| - | + | ||
| - | + | ||
| - | Update current password. | + | |
| - | | + | |
| - | My Account Dashboard: Change Password / Edit Profile | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | Update current email on file. | + | |
| - | If the e-wallet feature is enabled, customers can transfer funds from their e-wallet to another customer on | + | |
| - | the platform. To complete a transfer, they must enter the amount and the recipient’s email address, which | + | |
| - | must be linked to an active account. | + | |
| - | | + | |
| - | the admin panel. | + | |
| - | | + | |
| - | My Account Dashboard: Load Funds | + | |
| - | + | ||
| - | + | ||
| - | If the e-wallet feature is enabled, customers can load funds using any of the billing options currently | + | |
| - | enabled in the admin panel under the Deposit Configuration page. Any applicable load fees are also | + | |
| - | defined in that same section of the admin. | + | |
| - | | + | |
| - | My Account Dashboard: Load Funds | + | |
| - | + | ||
| - | + | ||
| - | This section is used to configure payouts, which are currently only supported via Stripe. To enable payouts, | + | |
| - | you’ll need to update the / | + | |
| - | have payout functionality enabled. | + | |
| - | Once configured, customers will have the option to withdraw funds from their e-wallet balance via Stripe. | + | |
| - | For more information, | + | |
| - | | + | |
| - | ● Stripe Connect | + | |
| - | ● Stripe Payouts | + | |
| - | | + | |
| - | My Account Dashboard: Create Stripe Connected Account | + | |
| - | + | ||
| - | + | ||
| - | If the e-wallet feature is enabled, customers can submit a request to upgrade their account in order to | + | |
| - | increase their daily limits for loading, transferring, | + | |
| - | These limits are defined in the Deposit Limits section of the admin panel, while upgrade requests can be | + | |
| - | reviewed and approved or denied in the Deposit Upgrade Requests page within the admin area. | + | |
| - | | + | |
| - | My Account Dashboard: Request Account Upgrade | + | |
| - | + | ||
| - | + | ||
| - | ACCOUNT | + | |
| - | | + | |
| - | API & Integration Resources | + | |
| - | Below are helpful links and documentation for integrating custom APIs and billing options with the platform: | + | |
| - | | + | |
| - | ● Custom | + | |
| - | API Guide (PDF) | + | |
| - | This document outlines how to create a custom API for the platform. | + | |
| - | | + | |
| - | ● Sample W | + | |
| - | | + | |
| - | | + | |
| - | All common biller integrations are added via the Add/Edit Site page in the admin panel. Below are links for supported providers: | + | |
| - | ● Stripe – | + | |
| - | Create API keys | + | |
| - | | + | |
| - | ● Elavon – | + | |
| - | Integration Guide (PDF) | + | |
| - | ● Nuvei – | + | |
| - | API Key Setup | + | |
| - | ● Payroc – | + | |
| - | API Integration Guide | + | |
| - | ● Square – | + | |
| - | Locations API Documentation | + | |
| - | | + | |
| - | ● Mastercard – | + | |
| - | Sandbox Setup | + | |
| - | Ask for Access or Info | + | |
| - | ● NATS, Sticky, Interac, and other billing options may require additional setup or may be discontinued. Please contact us for details. | + | |
| - | | + | |
| - | | + | |
| - | ● Persona Setup Guide | + | |
| - | | + | |
| - | | + | |
| - | + | ||
| - | ADMIN | + | |
| - | Nats compatible billers | + | |
| - | + | ||
| - | 2000Charge | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Boa Compra | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Click And Buy | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Epoch Systems | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | ICN Ltd. | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | OGO Shift | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | R18 | + | |
| - | | + | |
| - | | + | |
| - | Card Flex | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Vendo Services | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | WTS | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Alto Billing | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Focal Payments | + | |
| - | | + | |
| - | | + | |
| - | Greta 11 Billing | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Net Mobile | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Prime Orange | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Sonic Bill | + | |
| - | ADMIN | + | |
| - | | + | |
| - | + | ||
| - | Accounting - integrations | + | |
| - | | + | |
| - | Call Centers - Order | + | |
| - | Confirmation | + | |
| - | Argo Marketing Group | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Call Centers - Prospects | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Tazo Media | + | |
| - | Titan Leads | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Visa Order Insights | + | |
| - | Data Verification | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Yotpo Loyalty | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Red Crane Media | + | |
| - | Self Help Works | + | |
| - | | + | |
| - | | + | |
| - | A1 Payments Gateway | + | |
| - | ACI Pay.On Gateway | + | |
| - | | + | |
| - | Actum Gateway | + | |
| - | | + | |
| - | Adyen Gateway | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Alto Global Gateway | + | |
| - | | + | |
| - | | + | |
| - | Argus Gateway | + | |
| - | | + | |
| - | | + | |
| - | BCB Gateway | + | |
| - | Bill 1st Gateway | + | |
| - | Bill Pro Gateway | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Cart Connect Gateway | + | |
| - | | + | |
| - | Check 21 Gateway | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | CWB Pay Gateway | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Dry Run Testing Gateway | + | |
| - | | + | |
| - | E-Pro Gateway | + | |
| - | Easy Payments Gateway | + | |
| - | Ebanx Gateway | + | |
| - | eComm Merchant Solutions | + | |
| - | Gateway | + | |
| - | Edata Financial Gateway | + | |
| - | Edata Real Charge Gateway | + | |
| - | | + | |
| - | Gateway | + | |
| - | eGate Gateway | + | |
| - | | + | |
| - | ePay App Gateway | + | |
| - | ePay Machine Gateway | + | |
| - | | + | |
| - | | + | |
| - | ADMIN | + | |
| - | | + | |
| - | + | ||
| - | Maverick Gateway | + | |
| - | | + | |
| - | Maxx Merchants Gateway | + | |
| - | Meiko Pay Gateway | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Gateway | + | |
| - | NMI Gateway | + | |
| - | NMI PaySafe Gateway | + | |
| - | OGone Direct Link Gateway | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Payment) | + | |
| - | | + | |
| - | | + | |
| - | Pago Ipg Gateway | + | |
| - | | + | |
| - | Pay by Pago Gateway | + | |
| - | Pay Certify Gateway | + | |
| - | Pay Engine Gateway | + | |
| - | Pay Hub Gateway | + | |
| - | Paya Connect | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | PayU Gateway | + | |
| - | PPW Partners Gateway | + | |
| - | Prism Pay 2.0 Gateway | + | |
| - | | + | |
| - | | + | |
| - | PSI Gate Gateway | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Sage Pay Gateway | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Suite Pay Gateway | + | |
| - | | + | |
| - | USA ePay Gateway | + | |
| - | | + | |
| - | | + | |
| - | Wix Payments Gateway | + | |
| - | | + | |
| - | | + | |
| - | Zift Pay Gateway | + | |
| - | Ziri Pay Gateway | + | |
| - | | + | |
| - | | + | |
| - | Reach Gateway | + | |
| - | Risk Management | + | |
| - | | + | |
| - | | + | |
| - | Sales Tax | + | |
| - | | + | |
| - | Tax Jar | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Automation | + | |
| - | Acorn Logistics | + | |
| - | | + | |
| - | | + | |
| - | Blue Drone Fulfillment | + | |
| - | | + | |
| - | | + | |
| - | Dry Run Fulfillment | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | The Fulfillment Lab | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | iShip Solutions Fulfillment | + | |
| - | J.M. Field Marketing Fulfillment | + | |
| - | | + | |
| - | | + | |
| - | Nova Group Fulfillment | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Rapid Fulfillment | + | |
| - | Rhiem Fulfillment | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | Sykes Fulfillment | + | |
| - | | + | |
| - | | + | |
| - | Fulfillment | + | |
| - | UST Fulfillment | + | |
| - | | + | |
| - | | + | |
| - | 3 PL 2.0 | + | |
| - | | + | |
| - | | + | |