ProBusinessEnterprise

Bring Your Own Acquiring (BYOD)

What Is BYOD

BYOD (Bring Your Own Device merchant) — the ability to connect your own payment gateway instead of using the default gateway provided by tikento. Money from attendees goes directly to your bank account under your contract with the acquiring bank.

Why Connect Your Own Acquiring

Financial Benefit

The acquiring fee in tikento is pass-through: tikento does not mark up the bank's fee. You pay exactly what your contract with the bank specifies.

If you have high turnover and a direct contract with the bank on favorable terms (e.g., 1.5% instead of the standard 2.4%), BYOD allows you to use that rate in tikento as well.

Full Control

  • Money goes directly to your bank account
  • You can see all transactions in the bank's dashboard
  • Refunds are processed under your terms with the bank
  • Independence from tikento's payment infrastructure

Availability by Plan

PlanBYOD
FreeNot available
ProAvailable
BusinessAvailable
EnterpriseDefault (recommended)

On the Enterprise plan, your own acquiring is the standard configuration. The tikento commission on paid tickets on Enterprise is 0%.

Supported Gateways

The following payment systems are supported for BYOD:

GatewayPayment MethodsNotes
YooKassaCards, SBP, Apple Pay, Google PayMost popular choice
Tochka BankCards, SBP, Apple Pay, Google PayFor Tochka customers
StripeCards, Apple Pay, Google PayFor international events
CloudPaymentsCards, Apple Pay, Google Pay, SBPAlternative to YooKassa

If your gateway is not on the list — contact support for a compatibility assessment.

BYOD Setup

Step 1. Obtain API Keys from Your Bank/Gateway

Log in to your payment gateway's dashboard and obtain:

  • Merchant ID (merchantId / shopId)
  • Secret API key (apiKey / secretKey)

Specific instructions depend on the gateway:

Step 2. Connect the Gateway in tikento

  1. Open Settings → Payments.
  2. Click "Add payment gateway".
  3. Select the gateway type from the list.
  4. Enter the API keys.
  5. Click "Test connection".

Step 3. Configure the Webhook URL

After a successful connection, tikento will generate a unique webhook URL. Copy it and add it in your gateway's settings.

Without the webhook, tikento will not be able to automatically update payment statuses.

Step 4. Assign the Gateway to Events

After connecting the BYOD gateway, you can select it when creating or editing an event:

  1. Open the event → "Tickets" tab.
  2. In the "Payment gateway" section, select your connected gateway.
  3. Save changes.

Each event can use its own gateway — this is convenient if you have multiple legal entities.

Commissions with BYOD

When using BYOD, you pay two commissions:

  1. Bank acquiring fee — under your direct contract (pass-through, tikento does not mark it up)
  2. tikento commission — depends on your plan:
Plantikento Commission
Pro2% + 20 RUB per paid ticket
Business0.5% + 20 RUB
Enterprise0% (or 0.1% with dedicated SLA)

No commission is charged on free events (tickets priced at 0 RUB) on any plan.

Switching from Built-in to BYOD

When switching gateways:

  • Already paid registrations remain unchanged — refunds for them will go through the original gateway
  • New payments will be processed through the BYOD gateway
  • Historical reporting is preserved for both gateways

Frequently asked questions

Is BYOD available on the Free plan?
No. Connecting your own acquiring is available starting from the Pro plan. On Free, the built-in tikento gateway is used.
Will the tikento commission be lower when using my own gateway?
The tikento commission (percentage from each paid ticket) remains the same — it depends on your plan, not the gateway. Savings are achieved through a lower acquiring rate from your direct contract with the bank.
Can I use BYOD and the built-in gateway simultaneously?
Yes. You can connect multiple gateways and assign different gateways to different events.
What if my gateway is not supported?
Contact support — we are constantly expanding the list of compatible gateways. If your gateway supports a standard REST API with webhook notifications, integration is possible.