katching
PricingContact
Français
Sign in
Start for $1

Changelog

September 7, 2026

Version 2026.09.4

New, Improved

Payments, Admin

Back to the changelog

Activate Katching Payments without leaving Katching

Activating Katching Payments used to hand you over to a form that was not ours. It looked like a different product, it asked in a different voice, and it was the one place in your admin where Katching stopped being Katching.

That form is gone. Activation is now eleven short screens of our own: our fields, our questions, our words, and a summary at the end that shows you everything before anything is sent.

What it asks

Only what your business actually needs. A sole proprietor answers nine screens. A partnership answers eleven. Nobody is asked for an owner list who does not have owners, and nobody is asked twice for something we already know.

Where your sensitive answers go

Your Social Security number, your date of birth, your bank account number and any photo of your ID leave your browser for our payment processor directly. They never touch a Katching server, not even in passing, and nothing about them is written to a Katching database or a log. What we receive back is a token, which is a receipt, not a copy.

When you can start selling

As soon as the checks clear, usually in under a minute. Your bank account can wait: you can start selling first and add it later, and only your payouts wait for it.

If something is still missing

It appears on the same Payments page, as a Katching screen with a Katching sentence saying what is needed and by when. No error codes, no jargon from somewhere else.

  • /legal/katching-payments

Read this entry as markdown

katching

Katching, the operating system for brands that sell direct.

Noviantis Inc, a Florida corporation.

8400 NW 36th Street, Suite 450, Doral, FL 33166, United States

hello@katching.ai

+1 (786) 672-4903

TermsKatching Payments TermsAcceptable usePrivacyData processingSubprocessorsAI policyCookiesRefunds and cancellationLegal noticeAttributionsSecurityVulnerability disclosure