old_Loopcrypto.xyz
  • Introduction
  • Supported networks and tokens
  • Loop + Frames
  • Learn
    • How Loop works
    • Core components
      • Collecting authorization
        • Enabling payment on multiple networks
        • Accepting ETH and MATIC
      • Sending payment requests
      • Checking a customer's balance & allowance
      • Receipts and reminders
      • Customer portal
    • Loop + your financial stack
      • Linking on-chain transactions with invoices in your ERP system
      • Connecting with accounting software
      • Crypto off-ramp
    • Case studies
  • Dashboard functionality
    • Subscriptions
      • Free trials, discounts and more
      • Auto-invoicing
      • Auto-cancelations
    • One-time payments
    • Scheduling outbound payments
      • Internal notes
    • Editing an upcoming payment
    • Payments for platforms
  • Integrations
    • Stripe + Loop
      • Getting setup
      • Stripe Connect setup
      • Subscriptions
        • Free trials
        • Upgrading a customer or editing a subscription's products
      • Invoicing
      • One-time payments
      • Coupon codes
      • Stripe Connect - Subscriptions
      • FAQs about Stripe integration
    • Chargebee + Loop
      • Getting setup
      • Subscriptions
      • One-time payments
      • Coupon codes
    • Quickbooks + Loop
      • Invoicing
    • Xero + Loop
      • Invoicing
    • Ghost.org + Loop
    • Zapier + Loop
    • Manually add integrations
  • Technical Docs
    • APIs
      • Entity
        • Adding child entities
        • Adding user to child entity
        • Get child entities
      • Items
        • Adding items
          • Item types
          • Categories
        • Retrieving an item
        • Updating an item
        • Deactivating an item
      • Agreements
      • Transfer requests
        • Signing transfer requests
        • Loop CLI
        • Canceling transfer requests
        • Transfer request status
        • Handling unfulfilled transfer requests
        • Validations
      • Webhooks
        • Checking webhook signatures
        • Demo App
        • Slack, Airtable, Discord, Telegram
    • Archeticture
      • Smart contract
        • Deploying your smart contract
          • Modifying smart contract properties
      • Collecting authorization
        • Checkout page
          • Additional functionality
          • Add "pay with crypto" button
        • Checkout widget
          • NPM package readme
        • Checkout parameter examples
      • Providing on-chain payment based access
        • Subscription gated communities
    • Loop SDK
      • Verify Webhook
      • Transfers
      • Error Handling
      • Generating API keys
    • Sample guide: Collect a subscription or one-time payment
    • Integrating the Loop Protocol into your dApp
      • Payroll applications
      • Loan platforms (credit cards, BNPL)
    • Security
      • API Authentication
      • Securing with signatures
      • API Trust assumptions
      • Audits
  • FAQs
  • Company Dashboard
  • Loop Portal
Powered by GitBook
On this page
  • Collecting authorization
  • Requirements
  1. Learn
  2. Core components
  3. Collecting authorization

Enabling payment on multiple networks

PreviousCollecting authorizationNextAccepting ETH and MATIC

Last updated 1 year ago

Loop allows you to collect payment on several networks. The networks you are willing to accept payment on is controlled by the "accepted tokens" parameter. Including a token on a network unlocks that network.

You can only choose tokens that are in the smart contract. You can find the list of default tokens here. If there is an ERC-20 token you'd like to accept, please reach out to Loop so we can add the token to your contract.

Company dashboard

Navigate to the "subscriptions" page, click "edit" under "manage" and modify the accepted tokens list. You can add a new network by adding a token on that network.

API

You can always edit the tokens you are willing to accept for a subscription or one-time payment on the dashboard or via the PUT Items call.

Stripe + Chargebee

By default any product brought in from these systems will have ALL the tokens saved in the contracts enabled. If you would like to limit the tokens, you will need to edit the item's accepted tokens list.

Collecting authorization

When a customer uses the checkout page or modal they will be able to change networks and see only the tokens that are accepted on that network. If the user picks a network that is not supported, they will see a notification letting them know which networks are supported.

Requirements

You must have a smart contract deployed on the desired network. You can find a list of smart contracts on the Developer page. Reach out to Loop if you'd like to add a supported network.