- Platform Overview
- Resources and Guides
-
POS Integration
-
Getting Started
-
Core Concepts
-
Integration SDK
-
Certification
-
- Order Ahead
-
Provider Enablement
-
Provider Enablement
-
Endpoints
-
Developer Endpoints
-
-
API Reference
-
Getting Started
-
v15
-
- Access Tokens
- Campaigns
- Credit Cards
- Users
- Credit
- Locations
- Payment Methods
- QR Codes
- Progress Adjustments
- Orders
- Rewards
- Gift Cards
-
-
v14
-
- Credit
- Access Tokens
- Campaigns
- Categories
- Credit Cards
- Interstitials
- Locations
- Loyalty
- Orders
- Payment Tokens
- Support Tickets
- Users
-
-
LevelUp as Payment
Web Checkout / Sample UX Flows
The most basic way to use LevelUp is simply as a method of payment. In this scenario, the user flow is as follows:
Online:
- User logs in or registers for your site’s account.
- On the checkout screen, your site displays payment options and ability to add new ones.
- User selects “Pay with LevelUp”.
- You pass the user’s email as the
login_hint
to LevelUp’s OAuth Flow along with the requested permissions, such as:create_orders
orread_user_orders
. - User is redirected back to your
redirect_uri
with a one-time-usecode
param. - Use the
code
param to request anaccess_token
(as part of the OAuth Flow). - Store
access_token
on user’s account in your system.
In-App:
- User logs in or registers for your app’s account.
- On the checkout screen, you display payment options and ability to add new ones.
- User selects “Pay with LevelUp” and is deep-linked into the LevelUp application. The deep-link URL must be configured with the desired permissions.
- LevelUp presents a dialog to the user explaining the permission request.
- The user accepts or rejects it and is redirected back to your app with an
access_token
. Thataccess_token
can now be used to charge the user money, read their basic info, etc. Theaccess_token
LevelUp passes back both online and in-app can be stored on that users account for future usage, allowing the user to authenticate just one time.