Configurable functionality
Loop allows merchants to configure some functionality by appending parameters to the end of the Loop checkout page URL. These fields are case sensitive.
If you are appending multiple functionalities together, the first functionality requires the "?" and the other functionalities are appended with an "&" in place of the "?".
For example:
https://checkout.loopcrypto.xyz/<entity-id>/<item-id>?cartEnabled=false&defaultSpendingCap=<default spending cap>
Functionality
Functionality | Appended after item-Id | Description |
---|---|---|
Hiding the cart | ?cartEnabled=false | Hides the cart |
Pre-fill email | ?email= | Renders the email input uneditable |
Linking an authorization to existing subscriptions in Stripe | ?sub= | Payment will be for the next upcoming invoice for that subscription |
Passing an external ID | ?refId= | Id will be passed back in the webhooks |
Setting a minimum balance amount | ?minimumBalanceRequired | Requires the user to have a minimum amount in their wallet to complete checkout |
Setting a custom default authorization amount | ?defaultSpendingCap= | Override's Loop's default and suggests a new authorization amount |
Purchasing multiple products | ?item_id=<item_id>,<item_id>,... | Allow payment links to work for multi-product purchases |
Pre-fill email
You should pass in the encoded form of the email into the URL for it to properly handle special characters. For example, I should not pass "[email protected]" in the URL; instead, I should pass "andrew%[email protected]" in the URL for the email to display correctly on the checkout page as "[email protected]".
Payment links for a multi-product purchase
You can append multiple itemIds
together so that one payment link results in the purchase of multiple products. This includes combining multiple subscription products, one-time purchases or a combination of both (i.e. subscription(s) with one or many one-time payment). When combining multiple subscriptions, they must have the same billing frequency (i.e. monthly, yearly, etc.) and accept at least one of the same token/network pairs. Payment links will only display the token/network pairs that are accepted by all the products.
For example:
<https://checkout.loopcrypto.xyz/><entity-id>/<item-id>?item_id=<item_id>,<item_id>,...
Since you will need the itemIds
you will first have to create the product in Loop using the POST Items endpoint or retrieve an existing item using the GET Items endpoint.
Updated 21 days ago