Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Use the New User page to create new User Profiles.

Table of Contents
minLevel1
maxLevel2
include
outlinefalse
indent
excludeTrending Now, Important Links, Need more Help?
typeflat
separatorpipe
class
printablefalse

Web User

Users can access any portion of the PayTrace Virtual Terminal through the Internet. Web user credentials will work for accessing the API.

  1. Select Web User for the User Type.

  2. Enter a User Name.

  3. Enter a Contact Name.

  4. Enter an Email Address.

  5. Enter a Sale Ceiling Amount of over 0.00 if the user will be permitted to process Sales.

  6. Enter a Refund Ceiling Amount of over 0.00 if the user will be permitted to process Refunds.

  7. Select the Permissions for the User being created.

  8. Click the Save button.

Note

Removing permissions from your user account will prevent you from having access to those features the next time you log in. Users may only add features they have permission to; you cannot add these permissions to your account without involving another PayTrace user.

Password Requirments

Note

Passwords expire every 90 days and must be updated.

  • Passwords must contain a mix of letters and numbers with at least eight characters.

  • At least one uppercase and one lowercase letter is required

  • Passwords must be changed at least once every 90 days.

  • Passwords expire after four consecutive failed login attempts.

  • Passwords must be unique and not match the previous four passwords used for the user profile.

API User

API user credentials are leveraged through 3rd party integration software. There is no expiration period for API User passwords (aka tokens). API User credentials do not allow access to the Virtual Terminal. API User credentials allow access only for a 3rd party software solution to communicate with the API. This approach is consistent with PCI DSS security compliance requirements.

  1. Select API User for the User Type.

  2. Enter a User Name.

  3. Enter a Password.

  4. Confirm the Password.

  5. Enter a Contact Name.

  6. Enter an Email Address.

  7. Enter a Sale Ceiling Amount of over 0.00 if the user will be permitted to process Sales.

  8. Enter a Refund Ceiling Amount of over 0.00 if the user will be permitted to process Refunds.

  9. Select the Permissions for the User being created.

  10. Click the Save button.

Password Requirments

Note

Do not create API user passwords that contain special characters. Certain special characters can cause issues when being read by the API.

  • Passwords must contain a mix of letters and numbers with at least eight characters.

  • At least one uppercase and one lowercase letter is required

  • API user passwords do not expire.

  • Passwords expire after four consecutive failed login attempts.

  • Passwords must be unique and not match the previous four passwords used for the user profile.


Detailed Help

Required Fields

The red * asterisk denotes whether a field is required.

Type of User

Signify whether you are creating a Web or API user.

User Name

It must consist of 6 to 15 alpha-numeric characters and should contain the user's unique ID that will be used to log into the PayTrace system.

Contact Name

It must contain 1 to 50 alphabetic characters and should include the user's full name.

Email Address

It requires a valid email address of 7 to 50 alpha-numeric characters and should contain the user's preferred email address. If the user forgets their password, their username will be emailed to this address at their request.

Sale Ceiling Amount

The maximum amount that may be processed as a Sale by the user. A value greater than 0.00 must be provided when selecting the Sale permission.

Refund Ceiling Amount

The maximum amount that may be processed as a Refund by the user. A value greater than 0.00 must be provided when selecting the Refund permission(s).

Optional Fields

Process Sales

Enables users to process sale transactions.

Process Forced Sales

Enables users to process forced sale transactions that have already been authorized offline.

Unreferenced/New Refunds

Enables users to process new refunds without referencing an existing transaction.

Process Voids

Enables users to void transactions.

Referenced/Existing Refunds

Enables users to process refunds only by referencing an existing transaction.

View Transactions

Enables users to search and view transactions.

Capture Transactions

Enables users to capture authorization transactions.

Settle Transactions

Enables users to settle transactions.

Checks

Process Sales

Enables users to process check sales.

Unreferenced/New Refunds

Enables users to process check refunds without referencing an existing transaction.

Manage Checks

Enables users to manage checks.

Referenced/Existing Refunds

Enables users to process check refunds only by referencing an existing transaction.

View Checks

Enables users to search and view check transactions.

Settle Checks

Enables users to settle check transactions.

Account

Manage Customers

Enables users to add and edit customer profiles.

Delete Customer

Enables users to delete customer profiles. To delete customers, you must haveManage Customer permissions.

Recurring Payments

Enables users to add and edit recurring transactions.

Manage Design

Enables users to change the color and logo of the PayTrace account.

Discretionary Data

Enables users to add and edit discretionary data fields.

Manage User

Enables users to add and edit user accounts and modify permissions.

Security Settings

Enables users to change security settings for the account.

Payment Link Settings

Enables users to edit Payment Link Settings.

Payment Link Design

Allows users to modify the logo and colors of the Payment Link.

Integration

Manage API

Enables users to manage the system integration with PayTrace.


Need more help?

Our support team will be happy to assist you.

If you are unsure where to go, try the search bar on the top right of any page.

If you cannot find the documentation you are looking for, please let our support team know so we can continue to improve this documentation.