- 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
-
-
User Permissions
Web Checkout / Core Concepts
When a user wants to pay with LevelUp from within your e-commerce experience, you’ll need an access_token
from them. As described in the Sample UX Flows section, there are a few ways that you could have received this access_token
:
-
A user connected their LevelUp account to an existing site account
- Online: The user enters their email and your app posts to the User Permissions endpoint with the desired permissions. The user receives a push notification with details of the permission request and then accepts or rejects it. If they accept it, you will receive a callback with the access_token. You can also poll an endpoint to check for the access token.
- Mobile: The user is deeplinked into the LevelUp App with a URI including the desired permissions as parameters. The user is presented with a dialog detailing the permission requests and accepts or rejects them. If they accept, we will redirect to your application with the access_token.
-
A user logged in with LevelUp using the User Permissions endpoint
- Online: Same flow as described above.
- Mobile: Same flow as described above.
A user registered with LevelUp from your experience using the User Registration endpoint (Enterprise SDK only. Please email enterprise@thelevelup.com for details.)
Your e-commerce engine is embedded in an app running the LevelUp SDK and an
access_token
is securely syndicated in session (Enterprise SDK only. Please email enterprise@thelevelup.com for details.)
Once a user is authorized, you’ll have their access_token
with the permissions that your app requested. This access_token
will be used to read addresses, receive basic personal information, perhaps even read transaction history, and of course be able to charge the user.