Ahosting Logo

Getting Started

How to Complete Your Payment Successfully

Most hosting payments complete without incident. When one does not, the cause is usually mundane; a billing address that does not match the card, or an automated fraud check on a first order, rather than anything wrong with the card itself.

Before you pay

Enter the billing address exactly as your bank holds it. Card issuers check the address and postcode against their records, and a mismatch is the most common reason a valid card is declined.

Abbreviations matter here. If the bank has "Street" and you type "St", some checks fail on it.

Use an email address you actually read, and not one on the domain you are about to set up. Receipts, renewal notices and password resets all go there.

What to do when a card is declined

Work through these in order rather than retrying.

Check the address and postcode against what your bank has. This is the answer most of the time.

Check the card details: number, expiry, security code. An expired card is easy to miss.

Consider your bank's own block. Banks decline international or online transactions they consider unusual, particularly a first payment to a hosting company. Your bank can authorise it in seconds, and there is nothing the host can do about this from their side.

Try a different card or PayPal. Fastest route past a bank-side block.

Do not retry the same card repeatedly. Several failed attempts can trigger a temporary block on the card, turning one problem into two.

A declined payment: check these in orderBilling addressmust match exactly whatthe bank holds; theusual causeCard detailsnumber, expiry andsecurity code,re-entered rather thanpastedThe bankinternational or onlinepayments may be blockedby defaultAnother methodbefore assuming thecard is at faultIf payment succeeded but nothing was provisioned, that is a support ticket, not a second payment.

Payment succeeded but nothing was provisioned

Usually a routine fraud review rather than a fault. First orders, mismatched billing details and unusual locations all trigger it.

You will normally receive an email asking to verify something. Replying to it is what releases the order, and that email frequently lands in spam, so check there before concluding you were ignored.

If nothing arrives within a few hours, open a ticket with the order number.

Duplicate charges

If you retried and now see two charges, one is very likely an authorisation hold instead of a completed payment. Holds disappear on their own, typically within a few days.

Check your statement rather than your banking app's pending list, which shows both the same way. If both have genuinely settled after a week, open a ticket with both transaction references.

Automatic renewal

Hosting renews automatically by default, which is what you want: an expired hosting account takes the site offline, and an expired domain can be lost entirely.

Two things are worth doing once. Confirm the card on file has an expiry date beyond your next renewal, since an expired card is the most common cause of a failed renewal. And make sure renewal notices go to an address you read.

If you would rather renew manually, you can turn it off, but then the reminder emails become the only thing standing between you and an offline site, so make sure they arrive somewhere useful. Understanding billing cycles goes over the mechanics.

The refund window

Ahosting offers a 30-day money-back guarantee on hosting. It applies to the hosting service; domain registrations are generally not refundable, because a registration is paid to a registry the moment it is made.

That distinction catches people who cancel in the first week and expect the domain fee back. The domain is yours (you can transfer it elsewhere) but the fee is spent.

Receipts and invoices

Every payment produces an invoice in the client area, downloadable as a PDF. If you need company details or a VAT number on it, add them to your billing profile before paying instead of asking for a reissue afterwards.

Once the payment goes through, the welcome email with your cPanel details is the next thing to look for. Activating your hosting service explains what to do with it.

A payment can succeed for one item on the invoice and fail for another, which is how a working site ends up with an expired domain. There is more in How to Read Your Hosting Invoice and What Renews When.

Check the order actually completed

A payment that succeeded and a service that exists are separate events, and the gap between them is where support requests come from.

curl -sI https://yourdomain.example/ | head -1
dig yourdomain.example A +short

Read the account details in the confirmation and confirm you can log in to the panel. A payment recorded with no account provisioned is usually a matter of minutes rather than a fault, and it is worth checking before assuming either.

Keep the confirmation. It carries the order reference, which is the fastest way to have any question about the purchase answered without a series of clarifying messages.

Know which payment method renews what

An account frequently holds several items renewing on different dates through the same method, and the failure of that method affects all of them at once.

Check the expiry date of the card on file against the renewal dates it covers. A card expiring between now and the next renewal is the most common cause of a service lapsing, and it is entirely avoidable.

Where more than one payment method exists, confirm which one each item actually uses. Adding a new card does not necessarily move existing subscriptions onto it, and the old one continues being attempted until it is removed. Understanding billing cycles covers the rest.