Processor Comparison
When choosing a processor, consider your onboarding and reporting requirements, the desired merchant experience, and any other operational needs.
If you have questions about processor capabilities, please reach out to .
| TSYS | PAYSAFE + FLEX BILLING | PAYSAFE | |
|---|---|---|---|
| Processing Capabilities | |||
| Online payments | ✓ | ✓ | ✓ |
| In-person payments | ✓ | In beta | |
| Bank-to-bank payments (ACH/EFT) | ✗ | ✓ | ✓ |
| Currencies | |||
| USD | ✓ | ✓ | ✓ |
| CAD | ✗ | ✗ | ✓ |
| Capabilities | |||
| Apple Pay | In-person payments only | ✓ | ✗ |
| Platform fees | ✗ | ✓ | ✓ |
| Card funding type | Available in Q1 '25 | Available in API response | |
| Merchant Pricing | |||
| Custom pricing for Amex payments | ✗ | ✓ | ✓ |
| Custom pricing for in-person payments | ✗ | ✓ | ✗ |
| Pricing template processing time | Instant | Instant | Up to 7 business days |
| Pricing change processing time | Implemented for the following month, if requested before the 12th of the month | Instant | Up to 7 business days |
| Billing Frequency | |||
| Daily | ✗ | ✓ | ✓ |
| Weekly | ✗ | ✓ | ✗ |
| Monthly | ✓ | ✓ | ✓ |
| Settlement Times | |||
| Next-day funding (NDF) | 7:30pm EST | 4pm EST; payments are batched multiple times a day | |
| Standard payout speed | 2:30am EST | 12am EST; payments are batched multiple times a day | |
| Payout Speed | |||
| Next-day funding (NDF) | Default | In beta, requires UW approval | Requires UW approval |
| T+0 | High-risk merchants | Default | Requires UW approval |
| T+1 | High-risk merchants | High-risk merchants | Default |
| Payout Type | |||
| Gross payouts | ✓ | In beta | ✗ |
| Net payouts | ✗ | ✓ | ✓ |
| Payout Frequency | |||
| Daily | ✓ | ✓ | ✓ |
| Weekly | ✗ | ✓ | ✓ |
| Monthly | ✗ | ✓ | ✓ |
| Reporting | |||
| Transaction-level fee details | ✗ | ✓ | ✓ |
| Interchange qualification data | ✓ | ✓ | ✓ |
| Onboarding | |||
| Expected approval times | Same day, unless pended for additional information. | ||
| Credit checks | A hard credit check will be performed on the application signee. Non-profits are exempt. | A credit check may be performed if additional verification is needed. | |
| Agreements and digital signature | Merchants can agree and sign by completing an in-app Docusign flow. | Merchants can agree and sign by clicking to agree in the application. | |
| Documents | Merchants classified as Charities or Religious Organizations who indicate 501(c)(3) status must upload a 501(c)(3) determination letter to submit their application. | Documents are not required to submit the application. However, additional documentation may be requested after submission. | |
| Risk | |||
| Funding holds | Merchants will receive an email notification from and TSYS. Document requests can be managed through the Dashboard or API to resolve the funding hold. | Merchants will receive an email notification from . Document requests can be managed through the Dashboard or API to resolve the funding hold. | |
| Disputes | Disputes can be managed through the Dashboard or API. Merchants will receive an email notification from and TSYS. TSYS's email subject will be "Chargeback Notification" and the sender is cb_dispatcherlogin@transfirst.com. | Disputes can be managed through the Dashboard or API. | |
| In-person payments | |||
| Supported countries | US | US, CAD | |
| Devices | Valor VL100, VL110 | PAX A920, A920 Pro, and A80 | |
| Custom pricing for in-person payments | ✗ | ✓ | ✗ |
| Manual capture | ✓ | ✗ | |
| On-device tipping | ✓ | ✓ | |
| Printed receipts | Managed through the Dashboard or API | Managed directly on the terminal reader | |
| Card tokenization | ✓ | Available in Q4 '24 | |
| Real-time terminal monitoring | ✓ | ✓ | |
| Terminal management | ✓ | ✓ | |
| Point-to-point encryption (P2PE) | ✓ | ✓ | |