Company policy
This policy explains unpaid checkout exit, 72-hour failed-code reports, replacement-first review and refund boundaries for business orders.
Operator
Bulk Battle.net is the public trading brand. DIGITAL GOODS LTD is the legal operator and contracting entity for orders accepted through the service.
Policy
This policy covers wholesale business orders made under Bulk Battle.net, operated by DIGITAL GOODS LTD. Read it together with the Terms of Sale, Delivery and Code Fulfilment policy and the support workflow at /support/failed-code.
It does not create a blanket no-refund rule and does not remove mandatory rights that apply to a buyer or transaction.
A buyer may leave an unpaid checkout attempt and a quote may expire. No refund is due for an unpaid attempt because no payment has been accepted.
After a timeout, check the private order status before submitting another payment. Do not create a second transfer blindly.
Checkout submission creates a pending order. Acceptance requires terminal provider success, catalog, price and availability revalidation, and inventory reservation. Cancellation and remedy consequences after payment or acceptance are handled under this policy and applicable mandatory law.
The service does not promise a cancellation right where the law does not provide one, and it does not waive a mandatory right.
Report a suspected failed code to [email protected] within 72 hours of the relevant fulfilment or discovery event. Include the order reference, affected market/currency/denomination and exact error.
Attach only safe, redacted evidence. Never email a raw code, copy or paste an access token, forward the magic link, or send passwords, seed phrases, private keys or wallet backups.
The operator may review the order reference, market, currency, denomination, product family, fulfilment record, displayed status, error text, time and safe redacted images. Additional non-secret evidence may be requested when reasonably needed.
The site is not a validity checker for unused codes. A failed-code report is a case for review, not automatic proof of a defect.
When an issue is confirmed and a replacement is operationally available, replacement is considered first and recorded against the affected line. Replacement is not promised before investigation and cannot be issued when the approved process cannot safely provide one.
If a confirmed issue cannot be resolved by replacement, the operator may consider a refund under the applicable remedy process and mandatory law. A refund is not automatic.
Before processing, the operator will confirm the payment asset, network, amount basis, exchange-rate treatment, fees, destination and expected timing where those details are relevant.
Underpayment, overpayment, wrong-network transfers, duplicate transfers and transfers sent after quote expiry are manual-review cases. The operator must not silently change the payable or fulfilled quantity.
Codes appear only on a protected order view after fulfilment checks complete. After terminal payment success and those checks pass, we target making codes available within 15 minutes; manual review or provider and inventory issues can extend that operational target. Resend access is order-scoped, rotatable and revocable with a maximum age of 24 hours; email contains the approved link, never the raw code.
Questions
Send the order reference and the minimum information needed to identify your question. Never send a raw code, access token, password or wallet secret by email.