Table of Contents

Developers Guide

Introduction to Support Wiki

The USAePay Wiki provides a wealth of documentation for developers, merchant and resellers wishing to integrate their website, pos application or third party software.

  1. Developing a payment processing application is a careful and tedious task. Merchant Services requires cooperation of several different entities such as a Merchant Bank, a Merchant Service Provider, a Processing Platform, the issuing Credit Card company, a Merchant and their developer, and of course us the USAePay gateway.
  2. how to use this document:
    1. This document is meant for reference and does not follow a step by step pattern.
  3. Further documentation: HTML Tutorial, all about POST & all about GET, all about SOAP

Connecting/Integrating Your Application

  1. System Requirements
    1. A Web Server capable of making requests over port 80 (www) and port 443 (https).
  2. Source Keys
  3. Choosing an API (API Comparison)
  4. Soap WSDLs
    1. RPC encoding
    2. DOC type
  5. Sandbox Server
    1. Client Side v. Server Side {added some content}
    2. Error Checking
    3. Shopping Cart & eStore
      1. Requirements
  6. Implementing
    1. Retail, Swiped Cards
      1. Receipt Printing
    2. Recurring Billing {added some content}
      1. Overview
      2. Set up new customer
      3. manage recurring billing cycles
      4. edit customer
      5. delete customer
    3. Payment Button (see 3.3)
    4. CoBranding & Customization
      1. Requirements
    5. Integrated Login
    6. Batch Processing
    7. Uploaded Batches
  7. Updating
    1. Developer Newsletters: {added}
    2. Transaction API Changes
    3. SOAP API Releases
    4. Specific Application and Library Releases:
    5. ePayCharge
      1. Download
    6. Wireless ePay - Mobile OS
  8. Appendixes
    1. Glossary of Terms {added} [needs to be checked for missing terms]
    2. Frequently Asked Questions [what are they?]
      1. Q: Is USAePay a terminal capture system or host capture system? A: Terminal Capture
    3. Troubleshooting