For those setting up a third-party gateway for payment processing and completing our Third-Party Gateway Form, the information below may help in retrieving the necessary credentials to help complete the setup.
Adyen
Username, Password, and API Key are found when generating API Credentials within Adyen and can be found by navigating to Developers > API Credentials in Adyen.
URL Prefix Random Name and URL Prefix Company Name are found by navigating to Account > Merchant Accounts within Adyen.
The following roles must be enabled by Adyen to successfully tokenize credit cards. MarketTime can not enable these features, it must be done by Adyen for your Adyen account.
- API Tokenize Payment Details
- API PCI
Authorize.net
https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001271
Braintree
https://developer.paypal.com/braintree/articles/control-panel/important-gateway-credentials
CyberSource (P12)
Elavon
The MerchantID, UserID, and PIN are required.
The Elavon account also needs to have Tokenization enabled for the account.
All three values live in the Converge portal at convergepay.com. Here's exactly where to find each:
ssl_merchant_id (Converge Account ID)
- Log into Converge at convergepay.com
- Look in the upper right corner of the screen after logging in — the Account ID is displayed there
- This is a short numeric ID (often 6 digits), and it is not the same as your standard Elavon Merchant ID
ssl_user_id
- In Converge, click the Employees button in the left-side navigation
- Find the API user (often named something like "apiuser") — this user needs to have API user status and admin-level permissions
- The Employee ID listed for that user is your ssl_user_id
- Note: you may need admin permissions in Converge to see the API user listed here
ssl_pin
- Click on the name of that same API user from the Employees list
- Click Show PIN (some sources reference this as being under User → Change PIN)
- Copy the 64-character alphanumeric string — that's your ssl_pin
- The PIN must be associated with the terminal tied to that user; if it was never generated, you can create one from that same screen
One thing worth confirming before you dig in: make sure the user you're pulling the PIN from has API access enabled on their account rights, and that the terminal associated with that user has Tokenization enabled
Fortis
Generating a User API Key - This will provide you with both the User ID (Username) and User API Key required.
API Location ID can be found by navigating to Locations → Edit Location
Default Deposit Account can be found by navigating to Locations → Edit Location → Settlement / Deposit Settings
Network Merchants (NMI)
Please note these credentials should be the same as what you use when logging in here: https://secure.apspaymentgateway.com/merchants/login.php?cookie_check=1&referrer=L21lcmNoYW50cy9pbmRleC5waHA_&qed=8c1116f4f94cffe72c735939374ddc62203fb68b2f8fae8fb52475074c07fa1a
PayTrace
Please note these credentials should be the same as what you use when logging in here: https://www.paytrace.com/login.pay
Quickbooks
Stripe
https://support.stripe.com/questions/what-are-stripe-api-keys-and-how-to-find-them
Versapay
Please make sure you are using the latest Versapay API: https://secure.versapay.com/
To setup API credentials, log into https://secure.versapay.com/account