Payments
Gett offers flexible payment options to match your integration approach. Choose the path that best fits your platform's needs.
| Approach | Description | Best For |
|---|---|---|
| Automatic (Marketfront SDK-only) | Gett handles payment collection | Don't have existing payment data |
| Card-on-File | Leverage your existing saved customer cards | Have existing payment data, want to maximize conversion. Required for Marketfront API and Marketfront AI. |
What is Card-on-File?
Card-on-File allows you to use payment methods your customers have already saved with your platform. Instead of requiring users to re-enter their card details, Gett securely proxies the payment data to the restaurant's payment processor.
"Card-on-file" doesn't mean storing raw credit card numbers. If your platform uses a payment processor like Stripe, Braintree, Square, Adyen, or any other major provider, you already have tokenized cards that qualify for Card-on-File integration.
When customers save their payment method on your platform, your processor stores the sensitive card data and gives you a secure token. Gett works with all major payment processors to securely translate these tokens—your existing payment infrastructure is all you need.
Why Card-on-File?
| Benefit | Description |
|---|---|
| Higher Conversion | Users complete checkout without friction—no new payment entry required |
| Seamless User Experience | Users existing payment methods are automatically available |
| Trust | Users don't need to share payment info with a new system |
How It Works
When a consumer places an order using Card-on-File, Gett acts as a secure bridge between your payment infrastructure and the restaurant's:
- Your platform provides a token reference — The
paymentTokenfrom your existing payment processor - Gett securely retrieves the card data — Using pre-configured, encrypted channels to your processor
- Gett re-tokenizes for the restaurant — The card is tokenized with the restaurant's payment processor
- The restaurant charges using their token — Payment is processed through the restaurant's own infrastructure
This token-to-token interchange ensures:
- Your systems never handle raw card data
- The restaurant receives a token compatible with their processor
- All sensitive data flows through PCI Level 1 compliant infrastructure
PCI Compliance
Gett maintains PCI DSS Level 1 compliance, the highest level of payment security certification. By integrating with Gett, your platform benefits from our secure infrastructure without the compliance burden.
Your platform stays out of PCI scope — you only pass token references, never sensitive card data.
Card-on-File Implementation
Card-on-File works slightly differently depending on whether you're using the Marketfront SDK or the Marketfront API.
| Integration | Session Creation | Order Placement |
|---|---|---|
| Marketfront SDK | Pass payment method metadata (for UI display) | Reference payment by paymentToken |
| Marketfront API | N/A | Reference payment by paymentToken |
| Marketfront AI | N/A | Reference payment by paymentToken |
Configuration & Setup
Card-on-File interchange requires a one-time configuration between your platform and Gett. This configuration establishes the secure channel for payment data retrieval.
To enable Card-on-File for your integration, contact your Gett representative. Our team will work with you to configure secure payment interchange for your specific payment processor and architecture.