Payment Policy
Shot Flow · Payment Policy · v1.0 · Effective 21 July 2026
| Field | Value |
| Operator | CHALET AQUARIUS LTD |
| Company number | 15587263 |
| Registered office | 20 Wenlock Road, London, England, N1 7GU |
| Trading name / brand | Shot Flow |
| Website | https://shot-flow.com |
| Contact email | info@shot-flow.com |
| Support / complaints | info@shot-flow.com (Monday–Friday, 09:00–17:00 UK time, excluding public holidays) |
| Governing law | Laws of England and Wales |
| Document version | v1.0 |
| Effective date | 21 July 2026 |
| Payment model: Shot Flow accepts payment for one-time digital-content Orders. The checkout must show the selected Asset or Bundle, currency, tax and final amount before the user submits payment. Shot Flow does not operate an automatic-renewal subscription under the current model. |
1. Purpose and scope
1.1 Purpose and scope standard. This policy explains pricing, authorisation, payment security, settlement, receipts, reversals and disputes. For purpose and scope, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
1.2 User duties for purpose and scope. Within checkout, authorisation, settlement, fraud controls, refunds and disputes, when purpose and scope requires user input, the user must give accurate and current information, use the available account or support route and take reasonable steps within the user’s control. Deliberate circumvention or materially misleading information may change the available outcome.
1.3 Related provisions for purpose and scope. Within checkout, authorisation, settlement, fraud controls, refunds and disputes, a question or correction about purpose and scope may be sent to info@shot-flow.com with enough detail to identify the relevant Order, account or interaction. Full payment credentials and unrelated personal information must not be sent by email.
1.4 How purpose and scope operates. To administer purpose and scope, Shot Flow uses provider authentication, 3-D Secure, transaction monitoring, manual review and reconciliation. Each control is selected for the stated purpose and must not be repurposed for an unrelated objective.
1.5 Outcome for purpose and scope. The rules on purpose and scope should be read with the Terms & Conditions, Refund Policy and Fulfilment Policy. Where two provisions address the same event, the more specific operational rule governs that event while mandatory law prevails over both.
2. Merchant and payment relationship
2.1 Merchant and payment relationship standard. CHALET AQUARIUS LTD is the seller while regulated or specialist providers process the selected payment method. For merchant and payment relationship, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
2.2 Limits on merchant and payment relationship. If merchant and payment relationship cannot be completed as expected, the response may include decline, pending review, reversal, refund, access suspension or dispute evidence submission. The response should address the affected Order, account, record or use rather than impose a broader restriction without reason.
2.3 Correction of merchant and payment relationship. For checkout, authorisation, settlement, fraud controls, refunds and disputes, operational delivery of merchant and payment relationship may depend on provider systems and the user’s device or network. A temporary technical limitation does not alter the underlying contractual or statutory position.
3. Age and payment authority
3.1 Age and payment authority standard. Checkout is available only to users aged 18 years or over who are authorised to use the selected payment method. For age and payment authority, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
3.2 Correction of age and payment authority. For checkout, authorisation, settlement, fraud controls, refunds and disputes, operational delivery of age and payment authority may depend on provider systems and the user’s device or network. A temporary technical limitation does not alter the underlying contractual or statutory position.
3.3 Outcome for age and payment authority. The rules on age and payment authority should be read with the Terms & Conditions, Refund Policy and Fulfilment Policy. Where two provisions address the same event, the more specific operational rule governs that event while mandatory law prevails over both.
4. Accepted payment methods
4.1 Accepted payment methods standard. Checkout displays the methods actually available for the user, location and transaction. For accepted payment methods, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
4.2 Information relevant to accepted payment methods. The normal treatment of accepted payment methods may be adjusted for issuer decisions, provider downtime, legal restrictions and non-excludable payment rights. Any adjustment must remain proportionate and must not remove a right that cannot lawfully be excluded.
4.3 Misuse safeguards for accepted payment methods. In applying accepted payment methods to checkout, authorisation, settlement, fraud controls, refunds and disputes, if an initial decision relied on incomplete information, the user may submit material new evidence. Shot Flow will reconsider the affected point without requiring repetition of information already held.
5. Currency, prices and taxes
5.1 Displayed currency. The standard storefront currency is GBP. Where another currency is expressly offered, checkout displays that currency and the final amount before authorisation.
5.2 Tax display. Applicable value added tax or comparable sales tax is calculated and displayed according to the checkout configuration and transaction information.
5.3 Issuer conversion. If the payment account uses another currency, the issuer may apply its own conversion rate and fee. Those issuer charges are not collected by Shot Flow.
5.4 Price correction. An obvious pricing or technical error may be corrected before acceptance. If payment was already captured, Shot Flow will offer the correct transaction or refund the captured amount.
6. One-time purchase model
6.1 No automatic renewal. The current service sells individual Assets and Bundles through one-time charges. There is no recurring subscription, auto-renewal or periodic membership fee.
6.2 No stored value. A download entitlement is not money, e-money, a deposit, a token, a gift balance or a transferable financial instrument.
6.3 Future recurring offer. Any future subscription would require clear renewal frequency, price, cancellation terms and separate agreement before billing begins.
6.4 No cash-out. Unused access rights cannot be redeemed for cash, transferred between accounts or exchanged outside the refund rules.
7. Checkout and order submission
7.1 Checkout and order submission standard. The user reviews product, price, billing details and immediate-supply consent before submission. For checkout and order submission, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
7.2 Misuse safeguards for checkout and order submission. In applying checkout and order submission to checkout, authorisation, settlement, fraud controls, refunds and disputes, if an initial decision relied on incomplete information, the user may submit material new evidence. Shot Flow will reconsider the affected point without requiring repetition of information already held.
7.3 Limits on checkout and order submission. If checkout and order submission cannot be completed as expected, the response may include decline, pending review, reversal, refund, access suspension or dispute evidence submission. The response should address the affected Order, account, record or use rather than impose a broader restriction without reason.
7.4 How checkout and order submission operates. To administer checkout and order submission, Shot Flow uses provider authentication, 3-D Secure, transaction monitoring, manual review and reconciliation. Each control is selected for the stated purpose and must not be repurposed for an unrelated objective.
8. Authorisation and order acceptance
8.1 Authorisation and order acceptance standard. Provider authorisation does not guarantee acceptance until security checks and final confirmation are complete. For authorisation and order acceptance, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
8.2 Decision criteria for authorisation and order acceptance. Within checkout, authorisation, settlement, fraud controls, refunds and disputes, a notice dealing with authorisation and order acceptance should identify what happened, the relevant effective time and the practical next step, unless disclosure would compromise security, another person’s rights or a lawful investigation.
8.3 Related provisions for authorisation and order acceptance. Within checkout, authorisation, settlement, fraud controls, refunds and disputes, a question or correction about authorisation and order acceptance may be sent to info@shot-flow.com with enough detail to identify the relevant Order, account or interaction. Full payment credentials and unrelated personal information must not be sent by email.
8.4 Controls for authorisation and order acceptance. A decision concerning authorisation and order acceptance may take account of order totals, provider status, authentication result, settlement record, refund reference and delivery evidence. The weight assigned to a record depends on reliability, context and any credible contrary material supplied by the user.
8.5 Correction of authorisation and order acceptance. For checkout, authorisation, settlement, fraud controls, refunds and disputes, operational delivery of authorisation and order acceptance may depend on provider systems and the user’s device or network. A temporary technical limitation does not alter the underlying contractual or statutory position.
9. Strong customer authentication
9.1 Strong customer authentication standard. The issuer or provider may require 3-D Secure or another strong customer authentication step. For strong customer authentication, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
9.2 Limits on strong customer authentication. If strong customer authentication cannot be completed as expected, the response may include decline, pending review, reversal, refund, access suspension or dispute evidence submission. The response should address the affected Order, account, record or use rather than impose a broader restriction without reason.
9.3 Correction of strong customer authentication. For checkout, authorisation, settlement, fraud controls, refunds and disputes, operational delivery of strong customer authentication may depend on provider systems and the user’s device or network. A temporary technical limitation does not alter the underlying contractual or statutory position.
9.4 Information relevant to strong customer authentication. The normal treatment of strong customer authentication may be adjusted for issuer decisions, provider downtime, legal restrictions and non-excludable payment rights. Any adjustment must remain proportionate and must not remove a right that cannot lawfully be excluded.
9.5 Misuse safeguards for strong customer authentication. In applying strong customer authentication to checkout, authorisation, settlement, fraud controls, refunds and disputes, if an initial decision relied on incomplete information, the user may submit material new evidence. Shot Flow will reconsider the affected point without requiring repetition of information already held.
10. Payment security and card data
10.1 Provider environment. Full card numbers and card security codes are entered into and processed by the payment service provider. Shot Flow does not intentionally store them in its own application systems.
10.2 Limited references. Shot Flow may receive a provider token, card brand, last four digits, billing country, authentication result, risk indicator, transaction identifier and status.
10.3 Security standard. The provider is expected to maintain applicable Payment Card Industry Data Security Standard controls for its processing environment.
10.4 User precautions. Users must not email full card numbers, security codes or online-banking credentials to support. Shot Flow will never request a card security code by email.
11. Fraud prevention and manual review
11.1 Automated checks. Device, location, transaction velocity, provider risk, authentication and billing consistency may be evaluated to protect users and the merchant.
11.2 Manual review. A flagged Order may remain pending for up to 24 hours while proportionate verification is completed. No licence is final while payment or acceptance remains unresolved.
11.3 Verification. Support may request non-sensitive proof of identity, authority or transaction context. Unnecessary information should be redacted.
11.4 Outcome. A review may approve, decline, cancel or refund the Order. A decline based on security does not imply wrongdoing and may not disclose controls that would enable evasion.
12. Receipts and payment descriptor
12.1 Receipt. After acceptance, the user receives an electronic confirmation containing the Order reference, merchant name, purchased item, amount, currency and delivery route.
12.2 Descriptor. The card statement may display SHOT-FLOW.COM or a closely related provider-formatted merchant descriptor.
12.3 Recognition. Users should compare an unfamiliar entry with the confirmation, amount and date and contact info@shot-flow.com where safe and practical.
12.4 Durable record. Users should retain the receipt because it supports licence verification, re-download, refund review and dispute resolution.
13. Settlement and pending transactions
13.1 Settlement and pending transactions standard. An issuer may place a temporary authorisation hold even where an Order later fails or is declined. For settlement and pending transactions, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
13.2 Misuse safeguards for settlement and pending transactions. In applying settlement and pending transactions to checkout, authorisation, settlement, fraud controls, refunds and disputes, if an initial decision relied on incomplete information, the user may submit material new evidence. Shot Flow will reconsider the affected point without requiring repetition of information already held.
13.3 Limits on settlement and pending transactions. If settlement and pending transactions cannot be completed as expected, the response may include decline, pending review, reversal, refund, access suspension or dispute evidence submission. The response should address the affected Order, account, record or use rather than impose a broader restriction without reason.
14. Delivery linkage
14.1 Delivery linkage standard. Payment completion is linked to the digital fulfilment process and does not involve physical shipping. For delivery linkage, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
14.2 Requests about delivery linkage. For checkout, authorisation, settlement, fraud controls, refunds and disputes, safeguards used for delivery linkage protect purchasers, rights holders, payment participants and the service. They may be tightened where a credible security or rights risk exists and relaxed after that risk is resolved.
14.3 User duties for delivery linkage. Within checkout, authorisation, settlement, fraud controls, refunds and disputes, when delivery linkage requires user input, the user must give accurate and current information, use the available account or support route and take reasonable steps within the user’s control. Deliberate circumvention or materially misleading information may change the available outcome.
14.4 Related provisions for delivery linkage. Within checkout, authorisation, settlement, fraud controls, refunds and disputes, a question or correction about delivery linkage may be sent to info@shot-flow.com with enough detail to identify the relevant Order, account or interaction. Full payment credentials and unrelated personal information must not be sent by email.
14.5 How delivery linkage operates. To administer delivery linkage, Shot Flow uses provider authentication, 3-D Secure, transaction monitoring, manual review and reconciliation. Each control is selected for the stated purpose and must not be repurposed for an unrelated objective.
15. Failed, declined or interrupted payments
15.1 Failed, declined or interrupted payments standard. A failed attempt does not create a paid entitlement and should not be repeatedly submitted without checking status. For failed, declined or interrupted payments, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
15.2 Correction of failed, declined or interrupted payments. For checkout, authorisation, settlement, fraud controls, refunds and disputes, operational delivery of failed, declined or interrupted payments may depend on provider systems and the user’s device or network. A temporary technical limitation does not alter the underlying contractual or statutory position.
15.3 Information relevant to failed, declined or interrupted payments. The normal treatment of failed, declined or interrupted payments may be adjusted for issuer decisions, provider downtime, legal restrictions and non-excludable payment rights. Any adjustment must remain proportionate and must not remove a right that cannot lawfully be excluded.
15.4 Misuse safeguards for failed, declined or interrupted payments. In applying failed, declined or interrupted payments to checkout, authorisation, settlement, fraud controls, refunds and disputes, if an initial decision relied on incomplete information, the user may submit material new evidence. Shot Flow will reconsider the affected point without requiring repetition of information already held.
15.5 Controls for failed, declined or interrupted payments. A decision concerning failed, declined or interrupted payments may take account of order totals, provider status, authentication result, settlement record, refund reference and delivery evidence. The weight assigned to a record depends on reliability, context and any credible contrary material supplied by the user.
16. Duplicate and incorrect charges
16.1 Duplicate and incorrect charges standard. Verified duplicate or wrong-amount processing errors are corrected under the Refund Policy. For duplicate and incorrect charges, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
16.2 Requests about duplicate and incorrect charges. For checkout, authorisation, settlement, fraud controls, refunds and disputes, safeguards used for duplicate and incorrect charges protect purchasers, rights holders, payment participants and the service. They may be tightened where a credible security or rights risk exists and relaxed after that risk is resolved.
16.3 Information relevant to duplicate and incorrect charges. The normal treatment of duplicate and incorrect charges may be adjusted for issuer decisions, provider downtime, legal restrictions and non-excludable payment rights. Any adjustment must remain proportionate and must not remove a right that cannot lawfully be excluded.
16.4 Decision criteria for duplicate and incorrect charges. Within checkout, authorisation, settlement, fraud controls, refunds and disputes, a notice dealing with duplicate and incorrect charges should identify what happened, the relevant effective time and the practical next step, unless disclosure would compromise security, another person’s rights or a lawful investigation.
16.5 Related provisions for duplicate and incorrect charges. Within checkout, authorisation, settlement, fraud controls, refunds and disputes, a question or correction about duplicate and incorrect charges may be sent to info@shot-flow.com with enough detail to identify the relevant Order, account or interaction. Full payment credentials and unrelated personal information must not be sent by email.
17. Refunds and credits
17.1 Refunds and credits standard. Approved credits are returned through the original method where technically and legally possible. For refunds and credits, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
17.2 Limits on refunds and credits. If refunds and credits cannot be completed as expected, the response may include decline, pending review, reversal, refund, access suspension or dispute evidence submission. The response should address the affected Order, account, record or use rather than impose a broader restriction without reason.
17.3 How refunds and credits operates. To administer refunds and credits, Shot Flow uses provider authentication, 3-D Secure, transaction monitoring, manual review and reconciliation. Each control is selected for the stated purpose and must not be repurposed for an unrelated objective.
18. Chargebacks and payment disputes
18.1 Direct route. A user may contact Shot Flow first with the Order, amount and reason so a duplicate, delivery or descriptor issue can be investigated promptly.
18.2 No waiver. Contacting Shot Flow is encouraged but does not waive a statutory, issuer or payment-network right or shorten an external deadline.
18.3 Accurate evidence. Shot Flow may provide the provider, issuer or acquirer with the receipt, consent record, product description, access logs, communications and refund history relevant to the dispute.
18.4 No double recovery. A user must not retain both a merchant refund and a chargeback credit for the same amount. A duplicate credit may be reversed through the applicable payment process.
19. Payment reversal and entitlement
19.1 Payment reversal and entitlement standard. A permanent reversal may suspend or terminate the corresponding digital entitlement. For payment reversal and entitlement, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
19.2 Related provisions for payment reversal and entitlement. Within checkout, authorisation, settlement, fraud controls, refunds and disputes, a question or correction about payment reversal and entitlement may be sent to info@shot-flow.com with enough detail to identify the relevant Order, account or interaction. Full payment credentials and unrelated personal information must not be sent by email.
19.3 How payment reversal and entitlement operates. To administer payment reversal and entitlement, Shot Flow uses provider authentication, 3-D Secure, transaction monitoring, manual review and reconciliation. Each control is selected for the stated purpose and must not be repurposed for an unrelated objective.
19.4 Outcome for payment reversal and entitlement. The rules on payment reversal and entitlement should be read with the Terms & Conditions, Refund Policy and Fulfilment Policy. Where two provisions address the same event, the more specific operational rule governs that event while mandatory law prevails over both.
20. Taxes, invoices and business details
20.1 Taxes, invoices and business details standard. The user is responsible for accurate billing and tax information and should request invoice corrections promptly. For taxes, invoices and business details, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
20.2 Correction of taxes, invoices and business details. For checkout, authorisation, settlement, fraud controls, refunds and disputes, operational delivery of taxes, invoices and business details may depend on provider systems and the user’s device or network. A temporary technical limitation does not alter the underlying contractual or statutory position.
20.3 Outcome for taxes, invoices and business details. The rules on taxes, invoices and business details should be read with the Terms & Conditions, Refund Policy and Fulfilment Policy. Where two provisions address the same event, the more specific operational rule governs that event while mandatory law prevails over both.
20.4 User duties for taxes, invoices and business details. Within checkout, authorisation, settlement, fraud controls, refunds and disputes, when taxes, invoices and business details requires user input, the user must give accurate and current information, use the available account or support route and take reasonable steps within the user’s control. Deliberate circumvention or materially misleading information may change the available outcome.
20.5 Misuse safeguards for taxes, invoices and business details. In applying taxes, invoices and business details to checkout, authorisation, settlement, fraud controls, refunds and disputes, if an initial decision relied on incomplete information, the user may submit material new evidence. Shot Flow will reconsider the affected point without requiring repetition of information already held.
21. Account, access and payment-method responsibility
21.1 Account, access and payment-method responsibility standard. The account holder must protect credentials and use an authorised payment method. For account, access and payment-method responsibility, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
21.2 Limits on account, access and payment-method responsibility. If account, access and payment-method responsibility cannot be completed as expected, the response may include decline, pending review, reversal, refund, access suspension or dispute evidence submission. The response should address the affected Order, account, record or use rather than impose a broader restriction without reason.
21.3 How account, access and payment-method responsibility operates. To administer account, access and payment-method responsibility, Shot Flow uses provider authentication, 3-D Secure, transaction monitoring, manual review and reconciliation. Each control is selected for the stated purpose and must not be repurposed for an unrelated objective.
21.4 Requests about account, access and payment-method responsibility. For checkout, authorisation, settlement, fraud controls, refunds and disputes, safeguards used for account, access and payment-method responsibility protect purchasers, rights holders, payment participants and the service. They may be tightened where a credible security or rights risk exists and relaxed after that risk is resolved.
22. Payment records and retention
22.1 Payment records and retention standard. Transaction and dispute records are retained for accounting, fraud, licence and legal purposes. For payment records and retention, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
22.2 Related provisions for payment records and retention. Within checkout, authorisation, settlement, fraud controls, refunds and disputes, a question or correction about payment records and retention may be sent to info@shot-flow.com with enough detail to identify the relevant Order, account or interaction. Full payment credentials and unrelated personal information must not be sent by email.
22.3 How payment records and retention operates. To administer payment records and retention, Shot Flow uses provider authentication, 3-D Secure, transaction monitoring, manual review and reconciliation. Each control is selected for the stated purpose and must not be repurposed for an unrelated objective.
23. Changes, support and complaints
23.1 Changes, support and complaints standard. Payment questions are handled at info@shot-flow.com under the version applicable to the Order. For changes, support and complaints, the provision is confined to checkout, authorisation, settlement, fraud controls, refunds and disputes and does not enlarge the user’s rights beyond the product description, Order confirmation or applicable law.
23.2 Misuse safeguards for changes, support and complaints. In applying changes, support and complaints to checkout, authorisation, settlement, fraud controls, refunds and disputes, if an initial decision relied on incomplete information, the user may submit material new evidence. Shot Flow will reconsider the affected point without requiring repetition of information already held.
23.3 Controls for changes, support and complaints. A decision concerning changes, support and complaints may take account of order totals, provider status, authentication result, settlement record, refund reference and delivery evidence. The weight assigned to a record depends on reliability, context and any credible contrary material supplied by the user.
23.4 Requests about changes, support and complaints. For checkout, authorisation, settlement, fraud controls, refunds and disputes, safeguards used for changes, support and complaints protect purchasers, rights holders, payment participants and the service. They may be tightened where a credible security or rights risk exists and relaxed after that risk is resolved.
23.5 User duties for changes, support and complaints. Within checkout, authorisation, settlement, fraud controls, refunds and disputes, when changes, support and complaints requires user input, the user must give accurate and current information, use the available account or support route and take reasonable steps within the user’s control. Deliberate circumvention or materially misleading information may change the available outcome.
Payment lifecycle and status matrix
| Stage / status | Meaning | Customer action | Merchant action |
| Submitted | Payment details have been sent for processing | Do not resubmit until status is known | Request authorisation and create a provisional Order |
| Authentication required | Issuer requires 3-D Secure or another challenge | Complete the issuer step accurately | Await authenticated result |
| Pending / under review | Authorisation or security review is incomplete | Monitor email and respond to a proportionate request | Complete review within the stated 24-hour target |
| Accepted / paid | Payment and Order acceptance are complete | Use the provided delivery route and retain receipt | Grant the licensed entitlement and issue confirmation |
| Declined | Issuer, provider or merchant did not approve the attempt | Check details or contact the issuer; avoid repeated rapid attempts | Do not grant entitlement; retain limited security evidence |
| Failed / interrupted | Technical process did not complete | Check statement before retrying | Reconcile provider status and release any orphan Order |
| Refund pending | Refund instruction was accepted but issuer has not posted it | Allow five to ten business days and then contact issuer | Provide refund reference and investigate exceptions |
| Reversed / charged back | Payment was permanently reversed or disputed | Provide accurate evidence through the issuer route | Suspend or terminate corresponding entitlement as appropriate |
Practical checkout and payment controls
1. Before payment, verify the product title, Bundle contents, licence label, currency, tax and final amount displayed at checkout.
2. Complete any issuer authentication in the same browser session and do not use repeated rapid attempts after a pending or declined result.
3. Retain the Order confirmation and compare the statement entry with the expected descriptor SHOT-FLOW.COM.
4. For an apparent duplicate, send both transaction dates and amounts without sending a full card number or security code.
5. For a refund, allow the stated issuer posting period after the provider reference is issued before escalating a missing credit.
Payment dispute evidence guide
1. For non-delivery: provide the Order reference, purchase email, time, browser and the access or error screen.
2. For an unrecognised charge: provide the amount, date, last four digits and whether another authorised household or business user could have placed the Order.
3. For a wrong amount: provide the checkout or receipt total and the posted statement amount, redacting unrelated transactions.
4. For a compromised account: reset credentials, notify the issuer where card misuse is suspected and contact Shot Flow promptly.
5. For an issuer dispute already opened: quote the dispute date and do not seek a duplicate merchant refund for the same amount.
Shot Flow · Payment Policy · v1.0 · Effective 21 July 2026 · Published on the website; subject to update; the current published version governs.