Account Settings

Configure your account under Settings.

This page covers everything in that area: your business profile, notifications, KYB status, the receiving wallet where your Bitcoin settles, team members and their roles, API keys, and account security.

Business profile

Controls what customers see on hosted payment pages and receipts:

• Legal business name.
• Display name (customer-facing): shown on hosted payment pages and receipts. A preview panel shows how it appears to customers.
• Customer-facing description.
• Business category (for example, E-commerce).
• Support email.
• Logo: upload PNG, JPG, or SVG up to 2 MB. The logo saves immediately when you upload or remove it, separately from the other fields.

Click Save changes to apply. Changes apply to customer-facing pages within about 60 seconds.

Notifications

Choose which events you want to be notified about, and where. Each event row has channels: Email, In-app, and SMS. Click Save preferences to apply.

KYB status

Shows your business verification status. To get verified:

1. Create your account at merchant.gobtcpay.com.
2. Email [email protected] to request verification.
3. Wait for our confirmation and onboarding information.

Receiving wallet and custody

Your receiving wallet is where your Bitcoin settles. Linking it is part of the minimum setup before your first sale.

Link your wallet

The Receiving wallet tab shows a one-time QR code. To link your wallet:

1. Open the GoBTC Pay app on your phone and go to Settings, then Merchant, then Link wallet.
2. Scan the QR shown on this tab to connect.

The dashboard then shows Waiting for the app to confirm. The code expires after about 10 minutes; if it runs out, reload the screen for a new one.

Once linked, the dashboard shows the connected address and the date it was linked, and you can unlink it later.

Where your Bitcoin is held

If your merchant account is non-custodial (the default), your Bitcoin is held at addresses of the receiving wallet you linked. Each payment gets its own receiving address, derived from that wallet's public key (xpub); when the customer pays in the GoBTC Pay app, the funds go to the wallet's first address (index 0) instead. These are single-signature addresses, not a multisig. GoBTC Pay keeps only the wallet's public key, not a private key: it prepares a withdrawal as an unsigned transaction and does not sign it. For a payment from the GoBTC Pay app, the latest authorized amount moves on-chain at settlement; a payment from an external wallet has no settlement step. How it reaches you depends on your settlement mode.

Change outputs

A withdrawal spends every confirmed UTXO on the addresses you select. If the transaction has change, it goes to the first address (index 0) of your linked wallet, the same address that receives in-app payments.

Why incoming balances need confirmations

A withdrawal uses only confirmed UTXOs. Funds still waiting in the mempool are left out until they confirm, because the transaction that created them could still be replaced or dropped.

Team and roles

Invite people to your merchant account and control what they can see. Open Settings, then the Team members tab.

Invite a team member

1. Click Invite member.
2. Enter an email and choose a role.
3. Send the invite. The person receives an emailed link to accept or decline.

The members table shows each Member, their Role, Status, and Last active. An Admin can change a member's role, remove a member, or revoke a pending invite that has not been accepted yet.

Roles

In short, Admin can do everything, while Manager is scoped to view-only operations (transactions and reports) with no access to configuration, stores, or settings.

API keys

A secret API key lets your server call the GoBTC Pay API, for example through one of the SDKs. Open Settings, then the API keys tab.

Create a key

1. Click Create key.
2. Enter a label, for example the name of the system that will use the key.
3. Click Create key and copy the key. It starts with sk_live_.

The key is shown only once. GoBTC Pay stores only a hash of it, so it cannot be retrieved later: afterwards the dashboard shows only the beginning of the key. If you lose it, rotate the key or create a new one.

Keep the key on your server and send it as a Bearer token in the Authorization header. Never put it in a browser page or a mobile app. Only secret keys (sk_live_…) are accepted.

Rotate or revoke a key

Open View details on a key in the list.

• Rotate (then confirm with Rotate key) issues a new secret for the same key. The previous secret stops working immediately, so update your server right away. The new secret is also shown only once.
• Revoke key disables the key permanently. Any integration using it stops working immediately, and the key cannot be restored.

Use an account-wide key

Keys created in the dashboard apply to your whole merchant account. The API also lets you create a key limited to a single store, but such a key is refused when it is used to create a payment or to manage webhook endpoints. For a server that creates payments or registers its own webhook endpoint through an SDK, use an account-wide key.

Security and account protection

Secure your merchant account, and understand the cryptographic exit path that keeps you in control of your Bitcoin. These settings live under Settings, then the Security tab.

Two-factor authentication (TOTP)

Require a one-time code from an authenticator app at sign-in. On the Security tab, find the Two-factor authentication card and click Enable:

1. Scan the QR or enter the secret in an authenticator app.
2. Confirm the 6-digit code.
3. Save your recovery codes somewhere safe.

After that, sign-in asks for a code. If you lose your authenticator, use a
recovery code.

Password

Use Change password on the Security tab to update your sign-in password (minimum 12 characters). If you are locked out, use Forgot password on the login screen.

For privacy, we always show the same "reset link sent" confirmation, whether or not the email is registered, so accounts cannot be enumerated.

Active sessions

The Active sessions section lists devices currently signed in, with their location and last activity, so you can review and revoke access.

Conditional Recovery: your exit path

Conditional Recovery applies to the 2-of-3 multisig wallet you pay from in the GoBTC Pay app, where GoMining holds only one of the three keys. Your receiving wallet does not need it: GoBTC Pay holds no private key to it (see Where your Bitcoin is held).

For the app wallet, Conditional Recovery lets you regain sole control of your funds if GoMining ever becomes unresponsive, refuses to co-sign, or shuts down, without its cooperation.

The offline Recovery Key is released to you under whichever comes first:

1. The operator confirms on-chain settlement of any pending state, or
2. A configured safety delay elapses after your recovery request.

You can then spend with your User Key plus the Recovery Key directly on Bitcoin.

Can GoMining freeze or seize my Bitcoin?

GoMining holds no private key to your receiving wallet, so it cannot spend or confiscate the Bitcoin paid to you there (see Where your Bitcoin is held). For the app wallet you pay from, not permanently: funds at the 2-of-3 multisig need two keys to move, and the server holds one of the three keys, so it cannot spend or confiscate your BTC outright, and the time-based fallback means it cannot block recovery indefinitely.

The remaining trusts are operational: the custody provider honoring its release policy, and (in operator-settled mode) GoMining's solvency during the credit window (see Settlement Modes).