How you get paid

Your subscribers pay you, directly. TG Access never holds your money, never takes a cut on the way past, and could not freeze your payouts if it wanted to. What it does is watch for the payment landing and open the door.

That arrangement has a name — bring your own keys — and it is why commission reaches you as a separate invoice instead of being deducted.

Setting a method up

Open Settings in the dashboard. You will see every method the platform supports, and whether you have configured it.

Fill in the fields for the one you want and press Save. That is all it takes for it to start appearing in your bot.

Stripe — cards, worldwide

1. Sign in to Stripe and go to Developers → API keys.
2. Copy the Secret key. It starts with sk_live_ for real payments, or sk_test_ while you are trying things out.
3. Paste it into Secret key here.
4. Optional but strongly recommended: in Stripe go to Developers → Webhooks, add an endpoint, and copy the signing secret (it starts with whsec_) into the second field.

Without the signing secret, card payments will not confirm themselves — you would have to approve every one by hand. With it, a subscriber pays and their invite arrives seconds later, with nobody waiting on you.

PayPal

Take the Client ID and Client secret from your PayPal business account's developer dashboard and paste both in. A personal PayPal account cannot be used to collect subscriptions.

Your subscribers are offered PayPal only once the Webhook ID is saved too; it is what lets PayPal checkout payments confirm themselves:

1. In your PayPal developer dashboard, switch to Live (to Sandbox only while you are testing), open Apps & Credentials and choose the app your Client ID belongs to.
2. Add a webhook to it. For its URL, paste the Webhook URL shown here on the PayPal card (its Copy button copies it whole) rather than typing it; it ends in /pay/paypal/ followed by your account's public ID.
3. Subscribe the webhook to these events: CHECKOUT.ORDER.APPROVED, PAYMENT.CAPTURE.COMPLETED, PAYMENT.CAPTURE.DENIED, PAYMENT.CAPTURE.DECLINED, PAYMENT.CAPTURE.REFUNDED, PAYMENT.CAPTURE.REVERSED and CUSTOMER.DISPUTE.CREATED, plus CHECKOUT.ORDER.VOIDED if PayPal's list offers it. Any other event is ignored.
4. Copy the webhook's Webhook ID. Here, on the PayPal card, paste it into Webhook ID and fill in Client ID and Client secret again too (the form never shows what is saved, and saves all the fields together), then press Save (Replace once keys are saved). Leave Environment empty for live; type sandbox in it only while you are testing.

Without the Webhook ID, PayPal is not offered to your subscribers: they cannot choose it to pay, and the PayPal card here and the PayPal screen in your bot say so until it is saved. To take PayPal payments without it, add PayPal as a manual payment method instead (a paid-package feature); each of those payments waits for you to approve it, like a manual transfer. With it, we check every notification that reaches your Webhook URL with PayPal, using the Webhook ID, before acting on it, and refuse any we cannot check.

USDT

Give the wallet address you want to be paid at and the network it is on. Getting the network right matters: a transfer sent on the wrong network is usually gone for good. See choosing the right network — the same rules apply to your own wallet as to paying us.

What we can and cannot see

When you save a key it is encrypted immediately. Afterwards the settings page shows you only enough to recognise it: whether a Stripe key is live or test and its last four characters, or the first and last characters of a wallet address. The key itself is never displayed again, to you or to anyone.

To change a key, type the new one over the top and save. There is no way to read the old one back out first.

Next: approving payments that arrive by hand.