VidSparks | Payment Policy | v1.0 | Effective 21 July 2026
| Field | Value |
| Operator | LOGIC OCTAVE LTD |
| Company number | 15587296 |
| Registered office | 20 Wenlock Road, London, England, N1 7GU |
| Trading name / brand | VidSparks |
| Website | https://vidsparks.com |
| Contact email | info@vidsparks.com |
| Support / complaints | info@vidsparks.com; Monday to Friday, 09:00-17:00 UK time, excluding public holidays |
| Governing law | England and Wales |
| Document version | v1.0 |
| Effective date | 21 July 2026 |
| Important: VidSparks accepts one-time payments for Token Packs through authorised third-party payment providers. No subscription or automatic renewal is created. The checkout shows the currency, pack quantity, total price and applicable tax before authorisation. Card data is entered in the provider environment, and statements should show VIDSPARKS or a recognisable provider variation. |
1. Scope and purpose
1.1 This Policy describes how payments for fixed and flexible Token Packs are initiated, authenticated, captured, recorded and connected to digital fulfilment. It also explains declined, duplicate, unauthorised, refunded and disputed transactions. The Terms & Conditions and Refund Policy provide related contractual and remedy rules.
1.2 VidSparks sells Token Packs on a one-time basis. Buying a pack does not enrol the user in a subscription, create recurring billing or authorise future charges. A new payment instruction is required for each later pack purchase unless a separate feature is expressly introduced with clear consent and terms.
2. Nature of transactions
2.1 A payment purchases a specified quantity of Tokens used solely for eligible processing within the Account. Tokens are digital contractual units, not money, electronic money, cryptocurrency or stored value. They cannot be redeemed, transferred, resold or withdrawn to a bank or wallet.
2.2 Fixed packs contain the quantity displayed on the product page. A flexible pack allows the user to select from available quantities or values before checkout. The final checkout summary, not an earlier promotional estimate, controls the quantity, currency and total authorised for the transaction.
3. Accepted payment methods
3.1 The checkout displays the payment methods currently accepted, which may include major credit or debit cards and other regulated methods made available by the PSP. Availability can vary by country, device, issuer, amount, risk controls and provider configuration.
3.2 A displayed method is not guaranteed to be accepted for every transaction. The PSP, issuer, card network, acquiring bank or VidSparks may decline or require additional verification. We do not accept cash, cheques, banknotes, cryptocurrency, barter or payment through an unauthorised intermediary.
3.3 The payer must use a payment instrument they are authorised to use and must not conceal the true payer, location or purpose. Corporate users are responsible for internal authority and expense controls. Use of a personal card for an organisation does not change the consumer or business status determined by law and the transaction context.
4. Billing currencies and pricing display
4.1 Prices are displayed in GBP, or another supported currency clearly displayed at checkout. The selected currency and total remain visible before the final payment action. If another supported currency is offered, the checkout clearly identifies it; the user should not rely on a search result, cached page or external advertisement that shows a different price.
4.2 A bank or wallet provider may convert the transaction and apply a rate or fee under its own terms. VidSparks does not control that conversion. The order receipt records the currency charged by the PSP and should be used when comparing the transaction with a bank statement.
5. Taxes and charges
5.1 The checkout states whether applicable tax is included or added and displays the total payable amount before authorisation. Tax treatment can depend on billing country, customer status and supplied tax information. A business customer is responsible for providing accurate tax details and for any reverse-charge or self-accounting obligation that applies.
5.2 VidSparks does not add hidden service fees after the final checkout summary. Separate issuer, cross-border, currency-conversion, overdraft or wallet fees may be charged by another institution and are governed by that institution. Users should review their provider terms where the payment currency differs from the account currency.
6. Authorisation and transaction completion
6.1 Submitting payment authorises the PSP to request approval from the issuer and to process the amount shown. A successful authentication or pending authorisation does not necessarily mean settlement is complete. The transaction completes when the PSP confirms capture or another final successful status accepted by VidSparks.
6.2 An issuer may place a temporary hold while deciding or after a failed attempt. Holds normally release according to the issuer timetable and are not funds received by VidSparks. A user should compare settled entries rather than pending entries when assessing a possible duplicate charge.
6.3 We may cancel an authorisation before capture where a risk, technical or pricing issue is detected. Where funds were captured and the transaction must be reversed, the reversal or refund follows the PSP process and may take several business days to appear.
7. Use of third-party payment providers
7.1 Payments are processed by authorised third-party providers and acquiring partners selected for security, geographic coverage and card-network compliance. The provider may act as our processor for checkout functions and as an independent controller for fraud, legal and network obligations.
7.2 The PSP may collect card number, expiry date, security code, billing details, device signals and authentication data directly. Full card details are not intended to pass through or be stored in VidSparks systems. We receive transaction references, status, amount, currency, limited card descriptor, billing location and risk information needed to administer the order.
7.3 Provider terms and privacy notices may appear during checkout. If the PSP is unavailable or withdraws a method, we may offer another method without liability for the provider interruption. A user must not attempt to bypass the approved checkout or send payment credentials through email or chat.
8. Security, verification and fraud controls
8.1 Checkout may use strong customer authentication, 3-D Secure or comparable issuer verification. Additional checks may include device, IP address, billing location, velocity, prior disputes, Account age and mismatch indicators. These controls protect cardholders, issuers, the Service and the integrity of Token delivery.
8.2 A transaction may be delayed for manual review for up to 24 hours. We may request limited identity or payment evidence, reduce transaction limits, block a device or decline the order. We do not guarantee that a user who passes one check will pass later checks because risk can change by transaction.
8.3 Users must protect their Account and payment device, use accurate information and report compromise promptly. We will never ask by email for a password, full card number, security code or one-time bank authentication code. Suspected phishing should be reported to the support address.
9. User payment responsibilities
9.1 Before payment, verify the Token quantity, model or pack limitations, currency, total, tax, Account email and descriptor. The payer is responsible for sufficient funds, issuer permissions and truthful billing information. Repeated attempts with false or changing information can trigger fraud controls.
9.2 Do not use another person payment instrument without authority, split transactions to evade limits, use a proxy buyer to conceal location, exploit checkout errors, or spend Tokens while planning to deny the charge. Such conduct may result in cancellation, Account restriction, evidence submission and reporting where lawful.
9.3 A user who manages an organisation Account must restrict payment access to authorised personnel and maintain internal approval records. VidSparks is not responsible for an internal dispute between an organisation and its employee, contractor or administrator where the payment was validly authorised through the Account.
10. Declined, failed or reversed payments
10.1 A decline can result from issuer policy, insufficient funds, incorrect details, authentication failure, geographic limits, network rules, sanctions, suspected fraud or provider outage. VidSparks may not receive the precise reason. The user should review the checkout message and contact the issuer when directed.
10.2 Do not repeatedly resubmit a payment without checking whether a prior attempt is pending or settled. Multiple valid submissions can create multiple purchases. If the interface reports failure but the bank shows a settled charge, contact support with the time, amount and last four digits so the PSP status can be checked.
10.3 A reversal occurs where an authorisation or captured transaction is cancelled or returned. Tokens may not be delivered, or may be removed if already credited. Where the reversal was erroneous and the user still wants the pack, a new successful payment may be required after the original status is resolved.
11. Duplicate charges and technical errors
11.1 A pending hold plus one settled transaction is not normally a duplicate. Two settled transactions for the same intended order require review of PSP references, checkout requests and Token credits. We correct a verified duplicate through refund, reversal or Account adjustment under the Refund Policy.
11.2 A manifest pricing, quantity or currency error can result in order cancellation before use, with a refund of captured funds. If the transaction has been partly performed, we assess a proportionate correction and applicable consumer rights rather than using a technical error to avoid a valid obligation.
12. Unauthorised transactions and security reporting
12.1 An unrecognised statement entry may appear as VIDSPARKS or a recognisable PSP variation. Check authorised users and Account purchase history, then contact info@vidsparks.com and the issuer promptly if the charge remains unrecognised. Do not disclose full card data in the report.
12.2 We may lock the Account, freeze Tokens, require credential reset and preserve access, authentication, payment and fulfilment records. We cooperate with the PSP and issuer and assess whether the payment was authenticated, whether the Account was compromised and whether value was used.
12.3 A good-faith unauthorised-payment report does not breach the Terms. False claims, use-after-dispute or coordinated chargeback abuse are prohibited. Our investigation and a card-network decision can proceed separately, and each body may reach an outcome under its own rules.
13. Refunds and relationship to the Refund Policy
13.1 The Refund Policy states eligibility, evidence and timing. Approved funds are returned to the original method by default and in the original transaction currency. Monetary refunds remove the corresponding Tokens and may affect Outputs or Account access where value has already been used.
13.2 We acknowledge complete requests within two business days and normally decide them within ten business days. After processing, the bank or wallet usually posts an approved refund within five to ten business days, but external timing can vary. A Token restoration is separate and may be completed more quickly after a verified generation failure.
14. Chargebacks, retrievals and disputes
14.1 A retrieval is a request for transaction information; a chargeback is a card-network dispute that can reverse funds. Users are encouraged to contact VidSparks first because missing Tokens, duplicate attempts or descriptor confusion can often be resolved before the issuer process. This does not waive any cardholder right.
14.2 When a dispute is opened, we may provide the PSP, acquirer, network or issuer with the receipt, checkout disclosures, authentication result, device and Account data, Token delivery, generation records, communications and refund history. We limit disclosure to information relevant to the transaction and dispute reason.
14.3 Related Tokens may be frozen or removed while a dispute is pending. We do not provide duplicate recovery through both a merchant refund and chargeback. If one route has already returned funds, the other is adjusted or contested to prevent double reimbursement.
15. Timing of delivery and Account crediting
15.1 After final successful payment confirmation, Tokens are normally credited promptly and ordinarily within 15 minutes. A manual review can extend delivery up to 24 hours. The Digital Product Fulfilment Policy explains how to check the balance and report a pending or failed delivery.
15.2 Payment completion and generation completion are different events. A pack is delivered when the Account can access the Tokens. A later Generation Request may take minutes or longer depending on model, queue, input and safety review. The estimated generation time is not an additional payment authorisation.
16. Payment records and audit trail
16.1 We maintain transaction references, amounts, currencies, status changes, Token credits, refunds, disputes and supporting security records for accounting, tax, fraud prevention, customer support and legal claims. Records are retained under the Privacy Policy and protected by access controls.
16.2 Receipts and Account history help users reconcile charges. Users should keep their receipt, note the Account email and review statements promptly. We may correct a ledger entry where PSP evidence and internal records show a manifest error, with notice where the change materially affects the user.
17. Geographic and legal restrictions
17.1 Payment methods and Service access may be unavailable in countries subject to sanctions, card-network restrictions, provider limitations or legal prohibitions. Users must not mask location, use a prohibited payment route or direct another person to buy on their behalf to evade a restriction.
17.2 We may decline transactions where supply, payment processing or the intended use appears unlawful. A decline does not imply wrongdoing and may be based on provider policy. Captured funds for a transaction that cannot lawfully proceed are returned through the original method where permitted.
18. Minors and payment authority
18.1 Users must be at least 18 and have legal authority to make the purchase. The Service is not intended for child-directed payment. A parent, employer or cardholder should not share payment credentials with an underage or unauthorised user.
18.2 Where a payer alleges lack of authority, we examine Account access, authentication, communications and use. Mandatory payment and consumer rights are preserved. We may suspend the Account while protecting evidence and preventing further charges or use of disputed Tokens.
19. Changes to prices, methods and rules
19.1 We may change pack prices, Token costs, supported methods or currencies for future transactions. The price shown in the final checkout summary applies to that purchase. A later change does not alter a completed order or retroactively charge additional money.
19.2 Promotions may have stated dates, quantities, eligibility and Account limits. We may withdraw a promotion before purchase, but will honour a valid completed transaction unless fraud, manifest error or law requires correction. Promotional Tokens remain non-cashable and non-transferable.
20. Service interruptions and processor downtime
20.1 Checkout can be unavailable because of maintenance, provider outage, network failure or issuer interruption. Users should not send credentials through alternative channels. We may temporarily disable a method or display a maintenance message until secure processing resumes.
20.2 If payment status is uncertain after an interruption, wait for the Account and bank status to settle before retrying. Support can check a PSP reference. We are responsible for reasonable correction of our records, but cannot control the time taken by an issuer or network to release a pending hold.
21. Contact and complaint route
21.1 Payment questions, duplicate-charge reports and unrecognised transactions should be sent to info@vidsparks.com. Include the Account email, transaction date, amount, currency, receipt or PSP reference and last four digits only. Support operates Monday to Friday, 09:00-17:00 UK time, excluding public holidays.
21.2 We acknowledge complete complaints within two business days and normally provide a substantive response within ten business days. A user may escalate material new evidence or a factual error. Issuer, regulator and court rights remain available where applicable.
22. Updates
22.1 This Policy may be updated for law, card-network requirements, provider changes, fraud controls or Service development. The current version is published on the website. A change governs future transactions and does not remove an accrued right or alter a settled payment without lawful basis.
22.2 If a material checkout rule changes, the user will see the applicable price, currency, method and total before the next authorisation. No automatic renewal is introduced by a policy update; a separate clear mandate and consent would be required.
22.3 This Policy and related non-contractual matters are governed by the laws of England and Wales. Mandatory payment, consumer and jurisdiction rights applicable to a payer or consumer in another country remain unaffected.
Lifecycle. Practical payment lifecycle overview
| Stage | What normally happens | Typical status | Key risk / control |
| Pack selection | User chooses fixed or flexible Token quantity and reviews restrictions | Cart / pending | Clear quantity, price and Account identity |
| Checkout | PSP collects payment data and requests authentication | Authentication required / authorised / declined | Secure provider page, SCA or 3-D Secure, accurate billing data |
| Capture | Successful authorisation is captured or settled | Paid / processing | Prevent duplicate submission; reconcile PSP reference |
| Token credit | Purchased Tokens are posted to the Account | Fulfilled / manual review | Ledger integrity, fraud review, 15-minute normal target |
| Generation use | Tokens are deducted when a request begins under displayed cost | Processing / completed / failed | Cost confirmation, provider status, automatic restoration on verified failure |
| Refund or dispute | Eligible remedy returns funds or restores Tokens | Refunded / disputed / reversed | Original method, evidence, no duplicate recovery |
Good practice for users before submitting payment
– Confirm you are signed into the intended Account and can access its email address.
– Review Token quantity, pack conditions, currency, tax and total price on the final checkout screen.
– Expect the statement descriptor VIDSPARKS or a recognisable PSP variation and keep the receipt.
– Use your own authorised payment method and complete issuer authentication without sharing codes.
– After submitting, wait for a clear result before retrying and check both Account history and settled bank entries.
– Contact support promptly if Tokens are missing, the amount differs, or the charge is unrecognised.
VidSparks | Payment Policy | v1.0 | Effective 21 July 2026. Published on the website; subject to update; the current published version governs.