Developer Documents
Introduction
Welcome to the EdgePay Developer Resource. Below is an overview of each of our APIs, interfaces, and some fundamental payments considerations. If you need help, use the links below to our technical resources that are ready to assist you on your journey. Please familiarize yourself with the tools to help you decide what would be the best combination for your project. As always, feel free to connect with our Developer Support Team if you have any questions.
| Developer Support: Phone | |
|---|---|
| 888.406.8915 | developersupport@gettrx.com |
Payments
Security and Risk
Fraud Management Service
Set up static, dynamic, or machine learning filters and capture results
More infoToken Service
Replace sensitive credit card or checking account info with a token you can safely store
More infoPivot
Exchange credit card data for a token in-session from browser back to your server
More infoAVS & CVV
Verify card/cardholder info for card-not-present customers
More infoData Intelligence
Dashboard
Check on your most recent payment activities using the EdgePay dashboard
More infoReporting
Use our online reporting to access critical info in real-time or set up to receive files for your system
More infoMachine Learning
Use your customer interactions to make business decisions
More info
Before you begin
| Topic | Discussion |
|---|---|
| AUTHORIZE AND CAPTURE OR SALE (CAPTURE TOO) | The credit card system is a 2-message system, with authorization preceding capture. Money only moves after capture. There are some good reasons for a 2-message system like tip adjust (final amount is less than or greater than the authorized amount), or if you ship your goods or deliver your services after the authorization date and time. But, if everything happens all at once, consider a sale payment that will automatically capture the transaction for you. |
| TOKENIZATION | Do you want to store credit card or banking information on your server? If not, consider using one of our token services. You can request a token separately via the API, or as part of the payment request. One-time tokens can be requested via the Pivot API. Also, tokens can be requested or managed in the processing center. |
| VERIFICATION ONLY | Sometimes verifying a card by using the address verification service (AVS only) or the security code (CVV or CVV2) may be helpful for some businesses. These are zero-amount services transactions but confirm that the person supplying the payment also knows the cardholder zip code and/or security code. ACS and CVV are also typically used on card-not-present payment transactions to verify the card is valid. |
| DON'T KNOW THE FINAL AMOUNT YET | Sometimes the final amount cannot be determined at authorization. You can adjust the final amount with a capture transaction and an adjust code specifying the new amount and tip and/or tax if applicable. |
| AVOID TRANSMITTING CARD DATA | If you want to avoid processing card data, consider Pivot. This API/Interface uses the customer's browser or even an employer browser and replaces the credit card with a 1-time token. |
| SPECIAL DATA NEEDS FOR CERTAIN BUSINESSES OR TRANSACTION | Some businesses and, in certain circumstances, transactions will benefit from more data. The additional data can improve interchange and reduce costs. Also, some card-issuing banks may require more data for card not present transactions. Below are some examples where more data may be required:
|
Start building now!
Access all of our API and interface tools here: