Skip to main content

2.First things to know

2.4 Payment Methods and Receiving Accounts

2.4.1 What Is a Payment Method?

A payment method is a configured channel through which investors can send funds when purchasing tokens for a specific asset. Each payment method defines how funds are received — whether via a blockchain wallet, a traditional bank transfer, or an integrated payment processor.

The platform supports three types of payment methods:

  • Web3 — accepts cryptocurrency payments directly on-chain via supported stablecoin contracts (e.g., USDT, USDC, DAI).
  • Manual — accepts traditional bank transfers (wire/SWIFT). The operator provides bank account details, which are displayed to investors during checkout.
  • Stripe — accepts fiat card payments through Stripe's payment processing infrastructure.

2.4.2 Payment Methods List

The Payment methods page displays all configured payment methods in a table with the following columns:

  • Provider name — the type of the payment method (Web3, Stripe, or Manual).
  • Created date — the date and time when the payment method was created.
  • Actions — a toggle switch that controls whether the payment method is currently enabled or disabled.

2.4.2.1 Enabling and Disabling a Payment Method

Each payment method has a toggle switch in the Actions column. The toggle has two states:

  • Enabled (green) — the payment method is active and available to investors on the website.
  • Disabled (grey) — the payment method is inactive and will not be shown to investors.

When you click the toggle to enable a disabled payment method, a confirmation dialog appears:

Enable [Provider]? Are you sure you want to enable [Provider]? This payment method will become available to investors on your website.

Click Enable to confirm, or Cancel to keep the current state. A similar confirmation dialog appears when disabling an active payment method.

2.4.3 Adding a New Payment Method

Step 1: Navigate to the Payment methods page from the left-hand menu.

Step 2: Click the Add Payment Method button in the top-right corner of the page. A modal dialog titled Add Payment Method will appear.

Step 3: In the Provider dropdown, select the type of payment method you want to create: Web3, Stripe, or Manual.

Step 4: Click Save Method. The system will create the payment method and redirect you to its configuration page. Alternatively, click Cancel to close the dialog without creating anything.

Step 5: Fill in the configuration fields specific to the selected provider type (see sections 2.4.4–2.4.6 below).

Step 6: Click Save Changes to save the configuration.

After saving, the new payment method will appear in the payment methods list. It is created in a disabled state by default — you need to enable it manually using the toggle in the Actions column once the configuration is complete.

2.4.4 Configuring a Web3 Payment Method

The Web3 payment method allows investors to pay using supported stablecoins directly on the blockchain. When you open the configuration page of a Web3 payment method, the header shows Payment method: Web3 along with its unique system ID.

The Configuration section contains the following fields:

  • Receiving wallet / account — the blockchain wallet address where investor payments will be sent. Enter the full wallet address in this field. This is the address that will receive all on-chain payments routed through this method.
  • Contracts — a multi-select dropdown that defines which stablecoin contracts investors can use for payment. Available options include USDT, USDC, and DAI. You can select one, several, or all contracts by using the Select all checkbox. Only selected contracts will be presented to investors during checkout.
  • Token lock duration (hours) — the number of hours that purchased tokens remain locked (non-transferable) after purchase. Set this value to 0 to disable the lock and allow immediate transfers.
💡 Losing access to the receiving wallet means losing access to all incoming investor funds routed through this payment method. It is crucial to securely store and manage the wallet's private keys and backup information.

Click Save Changes to apply the configuration.

2.4.5 Configuring a Stripe Payment Method

The Stripe payment method allows investors to pay using traditional fiat payment cards (credit/debit) through Stripe's payment infrastructure. When you open the configuration page of a Stripe payment method, the header shows Payment method: Stripe along with its unique system ID.

The Configuration section contains the following fields:

  • Stripe secret key — the secret API key from your Stripe account (begins with sk_live_). This key authenticates the platform's connection to your Stripe account and must be kept confidential.
  • Webhook secret — the webhook signing secret from your Stripe dashboard (begins with whsec_). This is used to verify that incoming webhook events are genuinely sent by Stripe.
  • Token lock duration (hours) — the number of hours that purchased tokens remain locked (non-transferable) after purchase. Set this value to 0 to disable the lock and allow immediate transfers.
💡 You can obtain the Stripe secret key and webhook secret from your Stripe Dashboard under Developers → API keys and Developers → Webhooks respectively. Make sure to use live mode keys for production environments.
For more details please follow https://docs.tokenizer.estate/4-3-stripe-payment/

Click Save Changes to apply the configuration.

2.4.6 Configuring a Manual Payment Method

The Manual payment method allows investors to pay via traditional bank transfer (wire/SWIFT). The bank account details entered here are displayed to investors during checkout so they can initiate a transfer. When you open the configuration page of a Manual payment method, the header shows Payment method: Manual along with its unique system ID.

The Configuration section contains the following fields:

  • Beneficiary name — the full legal name of the account holder or company receiving the funds.
  • Beneficiary address — the physical address of the beneficiary (account holder).
  • Beneficiary country — the country where the beneficiary is located.
  • Bank name — the name of the bank where the receiving account is held.
  • Bank address — the physical address of the bank branch.
  • Bank country — the country where the bank is located.
  • Bank SWIFT/BIC — the SWIFT or BIC code identifying the bank in the international banking network.
  • Account number — the bank account number of the beneficiary.
  • IBAN — the International Bank Account Number, if applicable.
  • Payment details — a free-text field for any additional instructions or reference information that should be displayed to investors when making a transfer (e.g., required payment reference format).
  • Token lock duration (hours) — the number of hours that purchased tokens remain locked (non-transferable) after purchase. Set this value to 0 to disable the lock and allow immediate transfers.
💡 All bank details entered here will be visible to investors during the purchase flow. Double-check that all fields are accurate before enabling this payment method to avoid failed or misdirected transfers.

Click Save Changes to apply the configuration.

2.4.7 Token Lock Duration

All three payment method types include a Token lock duration (hours) field. This setting defines how long purchased tokens remain locked (non-transferable) after a successful purchase.

  • A value of 0 means tokens are immediately transferable after purchase.
  • Any positive value (e.g., 1, 24, 168) means tokens will be locked for that many hours before the investor can transfer them.

This setting is configured independently for each payment method, which allows operators to apply different lock policies depending on the payment channel. For example, you might set a longer lock for manual bank transfers (to account for settlement time) while keeping the lock shorter or disabled for instant Web3 payments.

2.4.8 Best Practices

  • Wallet security. Choose a wallet provider that offers strong security controls, including multi-signature or hardware wallet options. Limit and strictly control access to private keys. Maintain secure backups of wallet credentials in multiple safe locations.
  • Bank account management. Ensure bank account details are accurate and up to date. Use accounts that support the currencies and jurisdictions relevant to your investor base.
  • Access control. Assign responsibility for payment method management to a trusted role within your organization. Restrict who can create, modify, or connect payment methods to assets.