Zuper Pay Fee Structure
Effective from : January 2025
Fee Structure
Fee Type |
Fee |
Card Present Transaction |
2.9% of the transaction amount |
Card Not Present Transactions |
3.2% of the transaction amount |
ACH |
1% with a cap of $5 |
Disputes (ACH and Card) |
$15 |
Terminal Fee
Fee Type |
Fee |
Tap to Pay on iPhone |
$4/month/user |
Tap to Pay on Android |
$4/month/user |
M2 Terminals |
$4/month/device |
Stripe terminals cost $59 and thereafter the recurring charges as mentioned above.
International Cards are charged 2% additional fees over the transaction fees mentioned above.
Card Migration
1. Migration Facilitation
- Zuper (“Provider”) will facilitate the migration of card data should the Client (“Customer”) wish to transfer card data from their existing payment service provider to Zuper’s platform.
- All card data migration must comply with Stripe’s policies and utilize the standard encryption protocols as detailed by Stripe.
- The Customer must provide Zuper with the following information for each card to be migrated:
- The customer ID from the existing payment gateway.
- The corresponding customer ID for the migrated Stripe customer.
- The token(s) generated for each card.
- The first and last name associated with each card.
- The email address associated with each card
- Zuper shall not be responsible for the completeness or accuracy of the migration if any of the above information is missing or inaccurate.
3. Costs and Pricing
- A one-time implementation fee of USD 2,000 will be charged for importing and mapping up to 10,000 card records.
- For migrations involving 10,001 to 20,000 card records, the implementation fee will be USD 4,000.
- For migrations exceeding 20,000 card records, custom pricing will apply and will be agreed upon in writing prior to commencement of the migration.
4. Mapping and Data Integrity
- Zuper will use the information and mapping file provided by the Customer to map card data to existing customer records within the Zuper platform.
- Zuper does not guarantee that all card records will be successfully mapped to existing customers in Zuper, as successful mapping is dependent on the completeness and accuracy of the information and mapping file provided by the Customer at the time of migration.
- The data provided to Zuper for mapping of the customer card information should be the same data as provided to our partner, Stripe.
- Any cards added/modified after the migration has been initiated would not be available in Zuper.
5. Timelines
- The duration required to complete the card data migration shall be contingent upon the timely receipt of all necessary information and data from the Customer’s previous payment service provider.
- The timeline for completion of the data mapping process shall be subject to Zuper’s reasonable efforts and will depend on the complexity of the migration and the volume of existing tasks and projects in Zuper’s implementation queue at the time of migration.
- Zuper does not guarantee a specific completion date for the migration and mapping process and shall not be held liable for delays resulting from late or incomplete data provision by the Customer or their previous payment service provider, or from internal scheduling constraints.
6. Liability and Constraints
- The Customer is solely responsible for providing all required data, including email addresses, customer IDs for both the existing and migrated Stripe customers, and all relevant tokens.
- Zuper shall not be held liable for any missing, incomplete, or inaccurate information, or for any records that cannot be mapped due to such constraints.