Billing

An account costs $15 a month, with everything included. Signing up, the dashboard, these docs and an API key are free: you pay when you connect your first account. Payments go through Stripe, and the dashboard's Billing page shows your plan, your card, your invoices and what you'll pay next. The terms are the full rules.

PricesCopy Anchor Link

Prices are in US dollars, before tax: GST is added for customers in Australia, and your invoice shows any tax. Every connected account holds a slot, whatever its state: running, stopped, or waiting for a correct password. In copy trading every account counts, the leader too.

Your first accountCopy Anchor Link

Connecting your workspace's first account starts its plan. The connect dialog opens Stripe's checkout for $15 (or $15 for each account already connected), and the account connects once the payment is recorded. The day you pay is your renewal date: the plan renews on that day each month (on the last day of a shorter month).

The workspace's owners and admins can start the plan, connect accounts and update the card.

SlotsCopy Anchor Link

Your plan pays for slots. A slot paid for this period stays paid until your renewal date, so removing an account and connecting another before then costs nothing more.

Connecting an account when every paid slot is in use buys a new one:

• It's charged at once to the saved card, prorated from the start of that day (UTC) to your renewal date. The connect dialog shows the price, before any tax, and the account connects only after it's paid. The workspace's owners get an email each time a slot is bought.
• If the price changed since you saw it (the day changed, or the plan renewed), the dialog shows the new price to confirm before anything is charged. If a paid slot freed up meanwhile, the account takes it and nothing is charged. If another account connected at the same moment took the slot just bought for this one, that slot stays paid (the other account uses it) and the dialog asks you to confirm the next.
• If your card asks you to confirm the payment (3-D Secure), the dialog sends you to Stripe's page to finish it; connect again after.
• If your card is declined, the account isn't connected and nothing else changes. Update the card on the Billing page and try again.
• If the broker refuses the login after the slot is paid, the slot stays paid: connecting again with the right password costs nothing.

On your renewal date, the plan is charged $15 for each account connected then, and the count of paid slots starts again from those accounts.

Removing accounts and ending the planCopy Anchor Link

Removing an account stops its terminal straight away. Its slot stays paid until your renewal date, and the rest of the period isn't credited.

This is for your shared plan; a dedicated server is cancelled on its own (see dedicated servers). With no shared accounts left, your plan ends on the renewal date and nothing more is charged. Connect an account before then and the plan carries on. After it ends, connecting an account starts a new plan, with a new renewal date.

Dedicated serversCopy Anchor Link

A dedicated server is your own server, with its own IP and no one else on it, in London or New York. Only a workspace's owners can order one, from the Billing page.

• Ordering. Choose the slots (5 or more) and the location, and pay for the first month through Stripe's checkout. The server is set up, usually within a day, and the order's page shows its progress. If it isn't live within 72 hours of your payment, the payment is refunded in full.
• Renewal. Each server is its own subscription. Its billing period starts again on the day it goes live, with credit for the setup time, and it renews on that day each month.
• Accounts on it use its slots, not your shared plan's. Connecting picks the server or a shared location; a full server takes no more until you add slots.
• More slots. Slots that fit on the server open at once, charged now and prorated to its renewal date. More than the server holds become an order: Pipsocket agrees a time with you to make the server bigger, and those slots are charged when they open.
• Fewer slots are billed from the next renewal, never below 5 or below the accounts on the server. From when you ask, the server takes no more accounts than the new number. There is no credit for the rest of the period.
• Cancelling. Removing a server's accounts doesn't cancel it. To cancel, a workspace owner emails support@pipsocket.com. The server runs to the end of its paid period; then the terminals of accounts still on it are stopped, never closed out, and the server is retired.

If a payment failsCopy Anchor Link

Billing never closes a position and never touches your kill switch. If a renewal payment fails, Stripe tries the card again over the following days, and these steps follow, counted from the day it first failed. These are the usual days: the Billing page, a banner across the dashboard and the emails show your dates, and a step can come later, for example when a notice goes out late. The workspace's owners and admins are emailed when the payment fails, at close-only, at least 72 hours before terminals stop, and when they stop; Pipsocket also tries to send a reminder a few days before close-only.

Pay before the plan is cancelled and your accounts come back by themselves: from the Billing page, update the card and pay, or pay the open invoice on Stripe's page. Once the payment is recorded, the billing hold is lifted and the terminals billing stopped start again, a few at a time; ones you stopped yourself stay stopped, and your own kill switch stays as you left it. A payment that lands while or after the plan is being cancelled doesn't restore it by itself: Pipsocket contacts you to put the plan back or refund it. After the plan is cancelled, connecting an account starts a new one.

While suspended, a terminal's status is stopped and calls that need it answer 503 account_not_connected. Your positions and pending orders stay at your broker, with their stop loss and take profit held there, and you can reach them from your broker's own MT5 app. Trailing stops and break-even moves run in Pipsocket, so they stop moving until the terminal runs again.

A dedicated server's subscription follows the same steps, for the accounts on it.

A slot charge declined while connecting an account isn't a failed payment in this sense: that account isn't connected, and nothing else changes. If a payment is disputed with the bank, new accounts can't be connected until Pipsocket lifts the block; trading carries on. Once the dispute is settled, email support@pipsocket.com.

The billing holdCopy Anchor Link

Close-only is a hold on each account the unpaid subscription pays for (the shared plan's accounts, or those on an unpaid dedicated server), set on the host that runs it. While it is on, the account refuses what the kill switch block refuses, from every source: your calls, the stream, TradingView alerts and agents.

• A refused call answers 423 billing_hold, and nothing is sent:

  Copy Text

  {
    "error": "billing_hold",
    "message": "The account is close-only because the workspace's payment is overdue: new orders and changes to pending orders are refused until the payment goes through. Closing positions, cancelling orders and setting stops still work."
  }

• A TradingView alert that would open or add is refused with the outcome billing_hold; exits still run.

• Nothing is closed or cancelled by the hold itself. It survives restarts.

• It is separate from your kill switch. Only paying lifts it: lifting the kill switch doesn't, and lifting the hold never lifts your kill switch. When both are on, a refused call answers 423 kill_switch_engaged.

Invoices and your cardCopy Anchor Link

Stripe emails receipts and invoices. On the Billing page, owners and admins can open Stripe's billing pages to change the card, read and download invoices, and edit the billing details and tax ID that invoices show. Questions about a charge go to support@pipsocket.com.