Merchant terms
These terms apply when your business applies to accept payments. They cover onboarding, documents, payout accounts, sandbox and live modes, and how a merchant account can be paused.
Updated 15 November 2026
1. Who these terms apply to
These terms apply to the business that opens a merchant on Tyvion Capital, and to the people that business authorises. The person who submits the application confirms they can bind the business.
A personal login is not itself permission to take live payments. Live payments stay unavailable until the merchant application is approved.
2. The application
You tell us the legal name, trading name, country, business type, contact, and the currencies you expect to process. Use the lists in onboarding. Do not invent a business type or a country code in free text when a choice is offered.
We review what you submit. Approval, a request for more information, or a refusal are all possible outcomes. You must not take live customer funds while the application is still in progress.
3. Business documents
Onboarding asks for document details so the application can be reviewed. The dashboard records the document type, file name, content type, and size. The file itself stays on the device you used. Tyvion Capital does not receive the file bytes from that step.
You must still be able to produce the underlying document if we, a provider, or a competent authority asks for it. A saved file name is not a substitute for the document.
4. Settlement account
You give a settlement account so approved payouts have a destination. After the account is saved, the dashboard shows the last four digits, not the full account number.
You are responsible for the account being yours, being able to receive the currency you process, and being kept up to date. A wrong account can delay a payout. Tell us before the next settlement run if the account changes.
5. Sandbox and live payments
Sandbox keys let you create test payments and webhooks. They are not a way to collect from a real customer.
Live payments turn on only when the merchant is approved to process. Until then, the dashboard explains that live payments are unavailable. Do not work around that control.
6. API keys and webhooks
Create keys in the developers area after onboarding. The secret is shown once. Rotate a key if it may have been copied, and stop using the old secret.
Webhook deliveries are signed. Verify the signature on your server before you fulfil an order. A payment page in the dashboard is not, by itself, proof that your order system has been updated.
7. Your team
Owners, admins, developers, and staff have different access. Give each person the smallest role that lets them do their job. Remove a person when they leave the business.
Suspending a teammate is a deliberate action. The dashboard asks you to confirm it. You remain responsible for what that person did while they had access.
8. Fees, settlements, and refunds
The commercial schedule agreed at onboarding states the fees and the settlement timing. The marketing site does not state a rate.
Refunds are started by your team against a payment, for an amount you confirm. Read the Refunds and disputes document before you promise a customer a refund time.
9. Pause and closure
We can pause live payments if onboarding is incomplete, if a risk alert is open, if acceptable-use rules are broken, or if we are required to. We will tell the merchant contact we have on file, unless the law stops us from doing so.
You may ask to close the merchant by emailing tyviontechnologies@gmail.com. Closure does not delete settlement, dispute, or audit records that we still need.
.png&w=3840&q=75)