General Information
- Which features are supported for each gateway?
- What information should be supplied when creating a ticket?
- Guide - required information when submitting a ticket
- B1 iPayment - Hardware Requirements FAQ
- iPayment - Known issue - Pop up warning "Looks like the server component is not running correctly"
- B1 iPayment Server Component - Add Credit Card worker
- B1 iPayment Server Component - Scheduled Actions worker
- B1 iPayment Server Component - Authorization Expired
- B1 iPayment Server Component - Internal Message Queue worker
- B1 iPayment Server Component - One-time Credit Card link worker
- B1 iPayment Server Component - One-time Credit Card integration worker
- B1 iPayment Server Component - PayNow link worker
- B1 iPayment Server Component - Overview
- I receive an error on the Add Credit Card page, what should I do?
- iPayment with limited licenses
- How long do Pay Now links last before they expire?
- Authorize.Net / Moneris Token Import Tool
- FAQ: iPayment - 'Looks like the server component is not running correctly' startup message
- Can you move or re-use tokens between different gateways?
- How does confidential information communicate between B1 iPayment to the gateway?
- How does iPayment deal with PCI Compliance?
- How does the iPayment Pay Now functionality work?
- iPayment Authorization Configuration options
- iPayment - saving Credit Card information on One Time Customers
- Helpful gateway links
- 'OK' button on the credit card form has disappeared
- Does iPayment support Visa's new Card On File?
- Testing 'decline' responses in Demo Mode
- Can iPayment upload unmasked credit card data to the gateway?
- Can I use the 64 bit Add-on together with the 32 bit Server-component and why is there no 64 bit server-component