User Guide
Table Of Contents
- User Documentation
- Last Update:
- September 24, 2005
- Introduction to AssureBuy
- Overview
- AssureBuy Setup
- Payment Gateway
- Installation and Setup
- AssureBuy Functionality
- Introduction
- AssureBuy Payment Processing Window
- Sales Order Processing
- Receivables Management
- Invoices
- Technical Support
- Appendix
- Glossary of Terms
- ACH
- Acquirer
- Acquiring Bank
- Acquiring Processor
- approval code
- Authorization
- Bankcard
- Batch
- buyer
- capture
- card issuer
- card verification value
- cardholder
- case sensitive
- chargeback
- chargeback fines
- cookie
- credit
- CVV2 Response
- document
- encryption
- expiration date
- floor limit
- Force
- frame relay
- hold
- home page
- hosted
- IntegriCharge®
- Internet
- invoice
- invoice hold
- issuing bank
- JCB
- Linked Transactions
- merchant account
- navigation
- order system
- Payment Gateway
- pending
- PO
- Port
- process
- Process Hold
- recurring orders
- Refund
- rejected check
- rejected payment
- resubmitted
- secure server
- settlement
- SSL
- swipe terminal
- transaction
- transaction result
- Unprocessed
- wire transfer
- Index
Figure 20: Transaction Result
Step 4 - Linked Transactions
A Great Plains document may have one or more associated AssureBuy
transactions. Once a transaction has been processed, additional "linked"
transactions may be added. For example, an Authorization transaction may
be later followed by a Capture transaction. These are treated as two
separate transactions by the AssureBuy Payment Processing application. In
the following example, the Capture transaction is created by selecting
Capture in the "Change To" field on the AssureBuy Payment Processing
window.
AssureBuy Payment Processing Microsoft Great Plains Dynamics/eEnterprise AssureBuy Functionality • 58