All the information you need to know

Capacity is Cool

With instant activation you can set up your account, configure your preferred payment gateway, and start sending text-to-pay requests today.

Authvia Gateway Guide

Select a gateway or processor to see the required fields.
Authorize.net
Authvia needs the client's: 
  1. API Login ID
  2. Transaction Key
** Owned by Visa, an authorize.net (or "auth.net") account is used in the payments industry to link to other payment gateways. If you ask about a client's payment gateway and it isn't on Authvia's Gold Partner list, ask if their payment provider can get them an authorize.net account to connect to them.

Key Notes:
  • Authorize.net supports both card and ACH payments
  • The authorize.net account must be set to "E-Commerce/Internet"
  • Authorize.net accounts don't work internationally
Client needs help finding their gateway credentials?
Agave
Authvia needs the client's: 
  1. Merchant ID
  2. Merchant Key
Key Notes:
  • Agave Pay supports both Card and ACH
  • The Merchant ID is located at the top of the client's Agave virtual terminal screen
  • The Merchant Key is a security value, and Agave Pay will need the client to either email them at support@agavepay.com or call them at 855-546-8749, option 2 to get this value for us.
  • After the gateway credentials are collected there are a few more steps to do:
    • Email ops@agavepay.com to let them know that the client needs to use Authvia's TXT2PAY. Agave Pay will then configure the proper TSYS settings for the client's gateway credentials and email when they are ready for use.
    • the TSYS TID must be enabled with "Hold Until Release" for TXT2PAY payments to authorize, and only Agave Pay can request this
Client needs help finding their gateway credentials?
  • Log in to Agave   
  • Email support@agavepay.com
  • Call 855-546-8749, option 2






   
Braintree
Braintree

Authvia needs the client's: 
  1. Username
  2. Password
  3. Merchant ID
Key Notes:
  • Braintree is a PayPal branded product

Client needs help finding their gateway credentials?



       
Chase Orbital
Authvia Needs the client's:
  • Chase Username
  • Chase Password
  • BIN
  • Terminal ID
  • Merchant ID
Key Notes:
  • Chase supports both Card and ACH
  • Chase has 2 different platforms - Global/Stratus and NAP/Tandem
    • If Global/Stratus then BIN = 1
    • If NAP/Tandem then BIN = 2
  • If the merchant is on NAP/Tandem you must use Chase's 12 digit PNS (Payment Network Services) number as the MID to get it to work

  • For any accounts wanting to use Chase, send Business Name, Company Contact (name/email), and Merchant ID to Reni Mathew at reni.mathew@chase.com. He will connect with internal RM and help get new MID/credentials created for AV

  • ** Reni is a VP of Sales so he will always try to get the customer a new MID. If the customer doesn’t want a new MID Reni most likely won’t touch it. You may have better luck with Tim Wilson Tim.Wilson@jpmorgan.com VP of merchant services or Gloria Tanner (480-514-3737)  gloria.tanner@chasepaymentech.com Account Manager

  • Example email:

    • Hi Reni, We have a new Chase Paymentech account that would like to use Authvia. Here’s information about their business:

    • Business Name

    • Contact Name/Email

    • Merchant ID

    Can you confirm that we can connect to their account, as well as the BIN that is associated? 

    Thank you!

    Johannah

  • We haven’t been able to confirm with anyone at Chase, but we believe these credentials are always static and should be hard coded on the Authvia side: Industry Type: EC, BIN: 000001, Terminal ID: 001, Username: PAY2DAYSO2541444133, Password: jyh4p89MrMKy2WrYSb5

    • Chase Paymentech CS Phone Number:1-800-254-9556. 





Log in to Chase       Click this link for instructions on getting your Chase MID
Elavon Converge
Authvia needs the client's: 
  1. Converge Account ID ("AID")
  2. User ID ("UID")
  3. Elavon PIN

Key Notes:
  • Elavon Converge supports both Card and ACH
  • Can contact Software Support at 1-800-377-3962 (Option 2, Option 2) and request API User credentials for Authvia.
  • ** Converge must be set to not require CVV2 in merchant’s portal
  • ** MSP MUST set a new TID as Ecommerce only, NOT try to attach it to an existing Retail TID
  • For NVA:
    • Patient Name is required on transactions. From Elavon: The 4009 error indicates they’re not sending a required field. They can change the requirements of fields as needed by navigating to Settings > Payment Fields in the Converge UI.
  • Getting Gateway Credentials: 
    • Our new contact Matt Bosse wants to handle setup for gateway credentials himself. Email the details to Matt at Matthew.Bosse@elavon.com. 
    • If for some reason Matt is unavailable, send your email request to both Maria Serna Perez (Maria.Serna-Perez@elavon.com) and Elavon Strategic accounts (strategicretailrelationships@elavon.com). You’ll get the credentials from this group by Cisco secure email




Log in to Converge        To get your credentials please contact Software Support at 1-800-377-3962 and request API User credentials for Authvia.
CyberSource
Authvia needs the client's: 
  1. CyberSource Merchant ID
  2. Merchant Key
  3. Merchant Secret
Log in CyberSource        Instructions to locate your Merchant ID.    Instructions to generate your Key and Secret
FISERV FirstData CardConnect / CardPointe
Authvia needs the client's: 
  1. CardPointe Username
  2. CardPointe Password
  3. Host
  4. Merchant ID ("MID")
  • Verify the endpoint/host from Fiserv (Will be different for each MSP)

  • For CardPointe, merchants need to create a support ticket requesting “Production Credentials”. This will generate a username and password that Authvia can use to authenticate to the merchant’s account. Merchants can create these tickets from within the merchant portal and the CardPointe support rep recommended this instead of calling so they don’t have to sit on hold. They will need a new username and password for every MID.

  • First Data acquired CardConnect. First Data and Fiserv merged.




Fullsteam
Authvia needs the client's:
  • Merchant ID
  • Password
  • Username

Key Notes:


Log in to Fullsteam        For assistance finding your Merchant Id, submit a request to Fullsteam Support
iPayment

Authvia needs the client's:
  • iPayment Username
  • iPayment Password
  • iPayment Merchant ID



Log in to iPayment       
Maverick
Authvia needs the client's:

For Card:
  • Terminal ID
  • API Key
For ACH:
  • Terminal ID
  • DBA ID
Key Notes:

  • Maverick supports both Card and ACH

  • Merchants can contact Maverick at (800) 464-9777 or support@maverickhq.com. Hours of operation 6am - 5pm PST



Log in to Maverick       Contact your sales agent to get your Terminal ID and API Key
NMI Gateway
Authvia will need the client's:
  • Security Key
Key Notes:


Log in to NMI       Click this link for instructions on getting your Security Key
Payrazr
Authvia needs the clients:
  • Username
  • Password
  • Payrazr ZId
  • Payrazr Cert ID
Payrix from Worldpay
Authvia will need the client's:
  • Merchant ID
Key Notes:

  • Payrix supports both Card and ACH

  • API Key is needed if the merchant is from a different referrer, that is not Authvia. We will honor if API Key is sent from a partner, but will sub in our API Key if none is sent. API Key must be set to Private and Active in Payrix.



Log in to Payrix        Click this link for instructions on how to get your Payrix Merchant ID
Payroc
Authvia needs the client's:
  • Token
Key Notes:
  • Payroc supports both Card and ACH



Log in to Payroc        Click this link for Payroc support
Paysafe
Authvia needs the client's
  • Account ID
  • Password
  • Username
Key Notes:
  • Paysafe supports Card

  • Username/Password are API credentials to be requested from support@paysafe.com

  • Account Id is the same as the Account Number in Paysafe

  • Adam Brenner (Adam.Brenner@paysafe.com) is able to sign merchants up for Paysafe



Log in to Paysafe        Click this link for instructions on finding your Paysafe API Key
PlugNPay
Authvia needs the client's:
  • API Key
  • Secret Key
  • Merchant ID
Key Notes:
  • PlugNPay supports both Card and ACH


Log in to PlugNPay       For assistance finding your Merchant Id, submit a request to PlugNPay Support
Stripe
Authvia needs the clients:
  • API Key

Log in to Stripe        Click this link for instructions on how to get your Payrix Merchant ID
USAePAY
Authvia needs the client's:
  • API Key
  • PIN
  • Merchant ID

Key Notes:
  • USAePay supports both Card and ACH



Log in to USAePay              Click this link for instructions on creating an API Key and PIN
 WorldPay Express
Authvia needs the client's:
  • Account ID
  • Account Token
  • Acceptor ID
Key Notes:


Log in to WorldPay             Please contact support@fisglobal.com to get your Account ID, Account Token and Acceptor ID


Authvia Official Black-Green logo
Instant Demo -- Try it out

By entering your mobile number you agree to receive text messages. Standard message and data rates may apply. Message frequency varies. Call 562-567-6776 for help. Text STOP to cancel.