When a Pepperi order is submitted the user can be directed to make an ePayment via your payment provider. The ePayment workflow defined is launched from within Pepperi, allowing them to enter their payment details. Payment is processed in the payment gateway interface and the user is then returned to the app.
ePayment requires online connectivity for the payment to be processed via the provider.
You may define if payment is optional or required at the time the order is submitted.
Pepperi's connector integrates with your payment provider using prebuilt connectors we have created for major providers. For other payment gateways a custom payment gateway connector is required (contact your project manager).
The payment gateway connectors support two modes:
- Basic - includes basic credit card payment processing
- Basic + Tokenization - includes basic processing as well as the ability to save credit card information for future purchases, so the buyer does not need to re-enter payment details each time . Pepperi uses a token that identifies the buyer to the payment provider (details are stored in the payment provider, and not in Pepperi).
Quick Setup Payment Gateway
Pre-built Payment Gateway connectors
- Authorized .Net
- Card Connect
- Credit Guard
- Splitit (provides Payment splitting functionality to installments)
Custom Payment Gateway connector
Pepperi can customize the connection to additional payment gateways (pending API or other available connection methods provided by the gateway). This requires a custom payment connection to be built by Pepperi Professional Services. Contact us for pricing.
Pepperi sends the payment and retrieves any response returned and displays it in Pepperi as the order status (Paid, Needs Payment, Payment Pending).
Contact your project manager to add payment to your integration.
Watch this quick 20 sec clip to see ePayment via PayPal in action:
Please sign in to leave a comment.