Kenya Digital Service Tax and Online Payment Products

This article is not tax advice. It provides general information to help developers understand how Kenya's Digital Service Tax may relate to online payment products. Tax law is complex, changes frequently, and depends on your specific business circumstances.

Before making any tax decisions, consult:

• The Kenya Revenue Authority (KRA) website for the current regulations and rates.
• A qualified tax professional or accountant registered in Kenya.
• Your legal counsel for questions about liability and compliance.

The rates, thresholds, and requirements mentioned in this article are based on publicly available information and may have changed since publication. [TODO: verify current DST rate and thresholds with KRA]. Always verify against the most current KRA guidelines.

Kenya introduced the Digital Service Tax as part of the Finance Act. The tax targets income derived from services provided through a digital marketplace or over the internet to users in Kenya.

The basic idea: if you earn money by providing digital services in Kenya, the government wants a portion of that income, regardless of whether your company is based in Kenya or elsewhere.

The categories of services generally covered include:

• Digital marketplaces. Platforms that connect buyers and sellers online. If you build a marketplace app that charges commissions, this is relevant.
• Downloadable digital content. Software, apps, e-books, music, videos, and other digital goods sold online.
• Subscription services. SaaS products, streaming services, online courses, and membership platforms that charge recurring fees.
• Electronic data management. Cloud hosting, data storage, and data processing services.
• Online advertising. Revenue from advertising on websites and apps.
• Other services delivered over the internet. This is a broad category. If your service exists primarily online and generates revenue, it may fall within scope.

What DST is not: it is not a tax on using the internet, not a tax on M-Pesa transactions, and not a tax on payment processing itself. It is a tax on the income you earn from providing digital services.

This is where it gets relevant for developers. If you build and operate a product that earns revenue through digital channels, you need to determine whether your business is liable for DST.

Resident businesses. If your company is registered in Kenya and provides digital services, DST may apply to the income from those services. However, the interaction between DST and income tax for residents has been subject to legislative changes. Check the current rules. For some periods, resident taxpayers have been subject to DST, while for others, the tax has applied primarily to non-residents. [TODO: verify current DST rate and thresholds with KRA].

Non-resident businesses. If you are a foreign company providing digital services to Kenyan users, you are generally liable for DST on income derived from Kenya. This is one of the main targets of the tax, aimed at global tech companies earning from Kenyan users without a physical presence in Kenya.

Developers as employees vs. business owners. If you are employed by a company and building their product, DST is your employer's concern, not yours personally. If you are a freelancer or run your own SaaS business, you need to assess your own liability.

A few scenarios for clarity:

• You build a SaaS product that Kenyan businesses pay for monthly. The subscription income from Kenyan customers may be subject to DST.
• You build a marketplace app that takes a commission on each sale. The commission income may be subject to DST.
• You build an e-commerce store that sells physical goods and accepts payment online. The sale of physical goods may not fall under DST, even if the payment is digital. The tax generally targets digital services, not physical goods sold online. But verify this with a tax professional.
• You integrate Paystack into a client's website as a freelance developer. You are providing development services, not a digital service to end users. DST likely does not apply to your freelance development fee. But again, confirm with a professional.

If your business falls within the scope of DST, you need to register with KRA. Here is the general process (verify current steps with KRA):

1. Get a KRA PIN. If you do not already have one, register on the KRA iTax portal. This is the foundation of all tax obligations in Kenya.
2. Register for DST obligation. On iTax, you add DST as a tax obligation to your PIN. This is separate from your VAT or income tax registration.
3. Determine your filing frequency. DST returns are filed periodically. Check the current filing frequency with KRA.

For non-resident businesses, KRA has established processes for registration even without a physical presence in Kenya. The iTax portal supports non-resident taxpayer registration.

The key point for developers: if you are building a digital product that earns revenue from Kenyan users, do not wait until you are making large amounts of money to look into this. Registration has deadlines, and late registration can attract penalties. Even if your product is in early stages, understand the requirements early.

Once registered, you need to file DST returns and remit the tax to KRA. The general process:

1. Calculate the tax. Apply the applicable DST rate to the gross income from your digital services derived from Kenya. [TODO: verify current DST rate and thresholds with KRA].
2. File the return. Submit the DST return on the iTax portal by the due date.
3. Remit payment. Pay the tax amount through the payment options available on iTax (including M-Pesa and bank transfer).

Record-keeping is important. You need to maintain records that show:

• Total revenue from digital services.
• Revenue attributable to Kenyan users specifically.
• The tax calculated and remitted.
• Supporting documentation for the revenue figures.

If you use Paystack, your Paystack dashboard provides transaction reports that show payments from Kenyan customers, amounts, dates, and fees. These reports are useful for calculating DST liability, but they are not a substitute for proper accounting records.

Your Paystack transaction exports can help you determine the total revenue from your digital service. Export the data, filter by currency (KES for Kenyan transactions), subtract Paystack fees to get your net income, and apply the DST rate to the gross amount (not the net). However, whether DST is calculated on gross or net income depends on the specific regulations in effect. Consult your accountant.

This is the part that confuses developers most. You have a product that earns money. Paystack takes a fee. KRA wants DST. VAT may also apply. How do these stack up?

Here is the general picture (exact numbers depend on current rates):

• Customer pays KES X. This is the gross transaction amount.
• Paystack deducts its fee. You receive less than KES X in your settlement. The fee varies by payment method. Check paystack.com/pricing for current rates.
• DST applies to your digital service income. The taxable amount depends on the current regulations. It may be applied to the gross income from the service.
• VAT may also apply. If you are VAT-registered (required above a certain turnover threshold), VAT is a separate obligation on your services.
• Income tax applies to your profits. After all expenses (including Paystack fees and taxes), your net profit is subject to income tax.

The important point: these are not alternatives. They stack. A Kenyan SaaS business could be paying Paystack fees, remitting DST, collecting and remitting VAT, and paying income tax. All on the same revenue.

This matters for your pricing. If you price your product at KES 1,000 per month, you need to know how much of that KES 1,000 you actually keep after all fees and taxes. Build a simple model that accounts for:

1. Payment gateway fee (Paystack's cut).
2. DST (if applicable).
3. VAT (if VAT-registered).
4. Income tax (on net profit).

Many early-stage developers price their products without thinking about this stack. Then they are surprised when the math does not work. Do the math early.

DST does not affect every product the same way. Here is how it maps to common product types built by Kenyan developers.

SaaS products. A subscription-based software product sold to Kenyan businesses is likely in scope for DST. The recurring subscription revenue from Kenyan customers is digital service income. If you accept payment through Paystack (or any other method), the tax obligation is on you as the service provider, not on the payment gateway.

E-commerce platforms. If you sell physical goods through an online store, the sale of the goods themselves may not be subject to DST. However, if you run a marketplace that charges commissions or listing fees, those fees are digital service income and may be in scope. The distinction between "selling goods online" and "providing a digital marketplace service" matters for DST.

Digital content. Selling e-books, courses, music, or video content online to Kenyan users is generally within DST scope. If you run a paid content platform that accepts payment through Paystack, the content revenue is digital service income.

Mobile apps with in-app purchases. Revenue from in-app purchases and premium features in apps used by Kenyan users may be subject to DST. If you also earn advertising revenue from Kenyan traffic, that may separately be in scope.

API services. If you provide a paid API (data services, communication APIs, or payment facilitation) to Kenyan developers or businesses, the API subscription or usage fees are digital service income.

In every case, the tax is on the income from the digital service, not on the payment method. Whether the customer pays via M-Pesa, card, Pesalink, or bank transfer through Paystack does not change the DST calculation. The payment method is the delivery mechanism for the money. The tax is on the money itself.

If you are building a digital product that earns money from Kenyan users, here is a practical checklist. This is not exhaustive and does not replace professional advice.

1. Determine if DST applies to your product. Review the current regulations on the KRA website. Look at the categories of digital services and assess whether your product fits.
2. Consult a tax professional. Before you do anything else, talk to an accountant or tax advisor who understands Kenyan digital tax law. The cost of a consultation is nothing compared to the cost of penalties for non-compliance.
3. Register with KRA if required. Get your KRA PIN if you do not have one. Add DST as a tax obligation on iTax if your product is in scope.
4. Set up your record-keeping. Track all digital service revenue separately. Use your Paystack dashboard exports as one data source, but maintain your own accounting records.
5. Build DST into your pricing model. Factor the tax into your pricing from the start. Raising prices later to cover a tax you forgot about is harder than pricing correctly from day one.
6. Automate where possible. If you have consistent monthly revenue, set calendar reminders for filing deadlines. Consider accounting software that supports Kenyan tax obligations.
7. Stay current. Tax law changes. Kenya has made multiple amendments to digital tax regulations over the past few years. Follow KRA announcements and review your obligations periodically.

A few things that developers frequently get wrong about DST:

• "Paystack handles the tax for me." No. Paystack is a payment processor. It collects money on your behalf and deducts its processing fee. It does not calculate, collect, or remit your tax obligations. DST is your responsibility as the business earning the income.
• "DST only applies to big companies like Google and Netflix." The tax was partly designed to capture revenue from large foreign tech companies, but the legislation may apply to businesses of any size providing digital services in Kenya. Check the current thresholds.
• "If I am paying income tax, I do not need to worry about DST." DST and income tax are separate obligations. Paying one does not exempt you from the other. However, DST paid may be offset against income tax liability in some cases. Consult your accountant.
• "DST is the same as VAT." No. DST and VAT are different taxes with different rates, different filing schedules, and different rules. You could be liable for both on the same revenue.
• "My product is free, so DST does not apply." If your product is free but you earn revenue from advertising, premium features, or data services, that revenue may be in scope for DST. Free-to-use does not mean no revenue.

For the broader context of regulatory considerations when building payment products in Kenya:

• CBK Payment Service Provider Rules Developers Should Know covers Central Bank of Kenya regulations for payment systems.
• KRA eTIMS and Payment Receipt Integration Considerations covers electronic tax invoice requirements that interact with your payment flows.
• Paystack in Kenya: M-Pesa, Pesalink, and the Daraja Question is the hub article covering all aspects of building with Paystack in Kenya.

For learning to build payment integrations professionally, the McTaba 26-week bootcamp covers payment systems, API design, and deployment for the African market.