Withdrawal policy

1. Introduction and your consent

The purpose of this policy is to make the path from balance to bank predictable. It explains the rules we apply to every withdrawal request so that you can plan around them rather than discover them. Using the withdrawal function constitutes acceptance of the policy's current version, which is always the one published on this page; the date and nature of changes are covered in the final section.

2. Available withdrawal methods

Withdrawals are available by Visa and Mastercard cards, by direct-entry transfer to Australian bank accounts, and to wallet-funded methods through the card behind Apple Pay and Google Pay. Payouts return, wherever the rails allow, to the method you used to deposit: card deposits pay back to the same card, wallet deposits pay back through the same wallet arrangement, and bank transfers pay to your verified bank account. This return-to-source discipline is a security feature as much as a convenience, because it ensures funds travel to destinations already proven to be yours.

Where a method's provider does not support payouts, the equivalent rail is used and you are told which one before confirming. Adding a new payout destination that differs from your deposit method is possible with verification, described in section 6.

3. Processing timelines

Card withdrawals are typically completed within 1 to 5 business days, with the final timing set by your card issuer and the card scheme. Direct-entry bank transfers are typically completed within 1 to 3 business days. Wallet-based payouts are typically completed within 24 hours. Each request first passes our internal verification stage, which for a routine request completes the same business day. Requests entered before 15:00 AEST on a business day begin processing that day; later requests begin the next. Weekends and Australian public holidays are not business days for any rail.

These intervals are what clients normally experience, not ceilings we promise on every occasion: circumstances outside our processing, such as an issuer's fraud review, can extend them. The methods page carries the current figures, and your request's status shows its stage while it runs.

4. Fees and charges

Worthamence charges no platform fee for standard withdrawals by any supported method. Costs that can arise are third-party ones, and each is disclosed where it can be anticipated: a payment provider may levy its own charge for its leg of the transaction, a currency conversion may apply where a payout currency differs from your account currency, and network charges can apply to movements of digital assets. Any amount that will be deducted is shown for your confirmation before a request is submitted, and a request you have not seen the full cost of can simply not be confirmed.

5. Withdrawal limits

The minimum withdrawal is A$40; below that, the administrative cost of processing exceeds the value of the payment, and the amount is better left to accumulate or to be withdrawn with future funds. Daily and monthly maximums scale with your tier and its verification level, and your dashboard shows the limits that currently apply to your account rather than making you recall them from a table. Requests above a defined threshold receive a senior verification pass before release, which adds processing time in single hours, not days, and is described in the next section.

6. KYC and AML checks on withdrawals

Identity verification under our AML and KYC policy is completed before the first withdrawal and refreshed where the framework requires it. Withdrawals are part of transaction monitoring: payout size, frequency and destination are compared against your account's established pattern. A first payout to newly added bank details is confirmed with you directly before release. These checks exist because the withdrawal moment is where a stolen account is cashed out, and they are the reason a criminal who somehow reaches this point usually fails here.

7. Why a withdrawal can be delayed or refused

Delays have specific causes: identity details that are missing, expired or mismatched; documents that arrive unreadable; a monitoring question that requires an explanation; settlement on the underlying funds not yet complete; a technical fault on a payment rail; or a legal or regulatory requirement that compels holding the payment. Each cause has a specific cure, and where a request is held you are told which cause applies and what would resolve it.

Refusals are rarer and narrower: payout details that cannot be verified as yours, indications that the request is not being made by the account holder, funds subject to an unresolved dispute, and directions from competent authorities. A refusal is always communicated with its reason category, and funds that cannot be paid out remain visible in your account rather than vanishing into an unexplained state.

8. Your responsibility

The details you enter for a payout are yours to get right. Account names must match the verification record, bank details must be complete and current, and card payouts require the card to remain open. Where a payment goes astray because instructed details were wrong, recovery depends on the receiving institutions and can be slow or, in the worst case, unsuccessful. Confirming digits, especially account and card numbers, before submitting takes seconds; treat the confirmation screen as a check rather than a formality, and never let another person dictate payout details to you.

9. Cancelling or changing a request

A withdrawal request can be cancelled from the dashboard while its status is pending, and the funds return immediately to your available balance. Amounts and destinations can likewise be edited while pending. Once a payment has been released to the rail, it can no longer be stopped or modified by us, exactly as a sent bank transfer cannot; any correction then depends on the receiving side. If you notice an error in a released payment, telling support the same day materially improves the odds of interception.

10. Support

Questions about a specific request, its status or anything in this policy go to [email protected] and are answered during support hours, Monday to Friday, 9:00-17:30 AEST, with request-specific detail rather than generalities. Include the request reference from your dashboard so the thread starts at the right place.

11. Changes to this policy

This policy can be updated to reflect changes in methods, rails, legal requirements or our procedures. Material changes are announced in advance on the platform and by email where they affect existing balances, and the updated version takes effect from its publication on this page. Requests already submitted are governed by the version in force when you confirmed them. The date of the current version is available from support at any time.