Payment Methods

6. Current checkout availability

Payment connection is a separate store setup step. A method is treated as accepted only when it is connected and actually available for the order at checkout. Do not assume that a card network, wallet or processor is accepted because you have used it on another WooCommerce store. The catalog and bag can display a price and selected size before an actual payment method is enabled. That selection is not a paid order. If checkout says that no payment methods are available, contact support before attempting a financial action elsewhere. The store does not ask you to bypass an unavailable checkout by sending card details through email.

Keep the product and selected size when asking about availability, and distinguish the payment question from a question about fit or delivery. Payment brands and processor capabilities will be described only after actual verification. A reference shop’s accepted-method badges do not establish this store’s checkout capabilities.

7. Reviewing a bag before any payment

Check the design, size, quantity and displayed amount after the bag finishes updating. A repeated add-to-cart action may increase the quantity. Remove an unwanted unpaid line before proceeding rather than treating the removal as a refund request. Each selected variation should correspond to the size you intend to receive. If a product link preselects a variation, review that label instead of assuming the link always starts with an empty selection. The bag is useful for comparing the actual order selection, but it does not prove successful payment, shipment preparation or a completed order.

If an amount appears inconsistent, explain the expected line and the displayed result. A product screenshot and selected variation can help identify the issue without exposing payment information. Support does not need a full card number to review an unpaid selection or a quantity calculation.

8. The product amount and delivery charge

The product price belongs to the jersey line shown for the selected item. Review the total as separate lines rather than assuming every charge is part of that product amount. Free shipping is configured for the United States, Canada, Australia and New Zealand under the store’s shipping policy. This does not provide a verified statement about every possible government assessment or an unconfirmed international service. A reference store’s promotion does not change the amount displayed here. Ask about a specific line when you need clarification and identify the country privately if it affects the question.

Before making a payment, review the actual total shown by a verified checkout. If the amount changes unexpectedly, pause and identify what changed: quantity, variation, address or another displayed line. The team should explain a real total rather than inventing a tax-inclusive promise or an unsupported destination charge.

9. Currency and statement questions

Catalog prices are displayed in US dollars. Any conversion or statement treatment by a real payment service depends on the actual connected method and your financial provider. Do not assume that a wallet or card issuer will display the same numerical amount in another currency. The store should not guess an exchange rate, foreign transaction fee or settlement date for a provider it has not verified. Ask the relevant provider about its own conversion terms when those details matter. For a store question, identify the order amount and the verified payment method without sharing confidential credentials.

A payment receipt and a financial statement can describe different stages of a transaction. Keep the actual order reference when asking support whether a store action occurred, and ask your provider about a statement entry that requires provider-specific interpretation. Neither the store nor a bag screenshot should be treated as a substitute for that provider’s verified record.

10. A missing order confirmation

A submitted form, a bag screenshot and a confirmed order are different records. If you expected a confirmation but cannot locate it, tell support what you can actually see and whether a real connected payment method was used. Check the email address you entered and ordinary mail folders without assuming that silence proves either payment success or failure. Support must review the actual order and payment records before confirming the state. Do not repeatedly submit payments to resolve uncertainty without first checking, because repeated actions can create separate financial attempts.

Send the relevant order reference if one exists and the approximate time of the attempt. You do not need to disclose a password, one-time authentication code or full card number. If no checkout method was available, say that clearly; the presence of an unpaid bag does not create a receipt.

11. An interrupted payment attempt

If a verified checkout flow is interrupted, distinguish a browser error from the provider’s actual transaction result. Closing a window or losing a connection does not establish that a payment was cancelled. Equally, a loading indicator does not prove success. Record the visible result and any order reference, then ask support to check the actual state before attempting the same purchase again. The store should not invent a processor error code or claim that an authorization expired without evidence from the real connected service. A recovery step depends on the facts of that attempt.

Describe the page and action that were interrupted, while keeping credentials and private authentication details out of the message. If your provider shows an unfamiliar entry, ask about the actual record. A support reply should identify what is confirmed and what still needs a provider check instead of assuming every interruption follows one pattern.

12. Duplicate purchases or payment concerns

Two bag entries are not the same as two completed orders, and two statement entries may require an actual provider record to interpret. Identify the order references and amounts you recognize rather than declaring that every repeated line is a duplicate charge. Support must distinguish separate purchases, incomplete attempts and any verified financial action. If you intended only one order, state that explicitly and ask which records exist. Do not remove a bag line and assume it cancels a completed order. Cancellation and refund decisions follow their own stage-specific policies.

A useful message gives the approximate attempt times and the outcome you expected. Obscure unrelated statement entries if you provide an image and leave full account numbers out. The team should review the real order scope before discussing a cancellation, correction or approved refund.

13. Changing an order before fulfillment

Payment questions and order-change requests should be stated separately. If you want a different size, quantity or address, use the order reference and describe the exact replacement detail. The team must confirm whether the real fulfillment stage permits the change. A request sent during a working time window does not automatically change a completed financial transaction or stop a carrier handoff. If the proposed change affects the amount, wait for a clear verified next step rather than sending an additional payment to an unfamiliar address.

Do not place a second order as an assumed correction unless you intend another purchase. Read the cancellation/change-order page and keep the conversation focused on what should happen to the existing order. Support should not infer permission for a new financial action from a general fit question.

14. Refunds to the original payment method

An approved refund is directed to the original payment method under the refund policy, with the store’s7-calendar-day timeline after approval. A return request, a parcel scan and an approved refund are separate events. Keep the approval date when asking about the timing. The store does not replace an unresolved processor fact with an invented transaction reference or claim that an unconnected payment brand has already returned funds. If the original method has changed or is inaccessible, ask support about the verified process for the actual payment record rather than supplying a new account through an unsolicited message.

Never send full card credentials or login codes to investigate a refund. Describe the order reference and approved amount, and distinguish the store’s approval from any provider-specific statement timing. A change from an exchange to a refund should be an explicit request so the intended financial outcome can be reviewed.

15. Suspicious requests for an extra payment

Verify a message that asks for payment through an unfamiliar link, especially when it claims to activate tracking, clear a failed delivery or release an order. The presence of a design name or plausible reference does not prove the sender’s authority. Compare the request with the order and actual shipment information, then contact the published support address. Do not disclose a password, card number or authentication code to establish that you received the message. The store does not treat an unverified message as a confirmed checkout method.

Keep the sender, requested action and reference needed to explain the concern, with unrelated private data obscured. Distinguish a genuine carrier or government notice from a store payment request only after verifying the source. A free-shipping configuration should not be used to guess the legitimacy of every external message.

16. Information needed for a payment question

Provide the order reference, displayed amount, approximate time and a short explanation of the result you expected. Name a verified method only if it was actually used, rather than choosing a brand from memory. If the issue happened before an order existed, explain the selected product and bag state instead. These details help support locate the relevant event without collecting confidential financial information. A screenshot should show the issue while hiding unrelated addresses, balances and account identifiers. The store should request only the facts needed for the specific investigation.

Keep one conversation for the same issue and add new evidence near the start of a follow-up. Do not send a full history of unrelated transactions. If the outcome you want changes, such as from checking an order state to requesting cancellation, state the new request clearly.

17. Verification before accepted-method claims

The store’s accepted-method information must match the actual checkout configuration and observed behavior. Logos alone do not establish availability, and a method that exists in software is not automatically enabled for every destination or order. Payment and fulfillment verification are separate facts: a successful method connection does not establish the supplier, material or delivery details of a jersey. Until the relevant setup is verified, ask about the actual available option rather than relying on a reference site’s badges or a generated product image.

When payment availability changes, the page should describe the confirmed method and relevant verified restrictions. The team must not invent wallet support, installments, security certifications or processor settlement guarantees. Review the checkout itself and contact support when the displayed options conflict with the information you were given.