NinerNet Communications™
Blog

Corporate Blog

Stanbic account number change

20 September 2016 13:17:12 +0000

We have just sent out an email to our Zambian clients about the fact that Stanbic have suddenly changed our account number, with no notice whatsoever or any indication if the old account number will work for an overlap period. Since sending out the email a few minutes ago we’ve heard from one client, who is also unfortunate enough to be a Stanbic customer, that they have heard there will be a one-year overlap period during which the old account number can be used, but we have not been able to confirm this with Stanbic ourselves.

The point of this blog post is to confirm that the email you received from NinerNet is indeed authentic. Thank-you for your time.

NinerNet home page

Subscriptions:

RSS icon. RSS

General Information:

This is the corporate blog of NinerNet Communications. It's where we post announcements, inform and educate our clients, and discuss issues related to the Internet (web and email) hosting business and all that that entails. This includes such concomitant industries and activities such a domain registration, SSL certificates, online back-up, virtual private servers (VPS), cloud hosting, etc. Please visit our main website for more information about us.

Search:

 

Recent Posts:

Archives:

Categories:

Tags:

accounts receivable apple billing branding cira client feedback contact information domain registration domain registry of canada domain renewals domains domain sales dot-ca domains dot-zm domains down time droc facebook google happy hosting customers hosting transfer icann internet registry of canada invoices iphone iroc kwacha maintenance new services paying your bill paying your invoice quarterly kwacha rate review rates registrant transfers registrar transfers reputation scams search engine optimisation search engine optimization security seo service hours support testimonials transparency verisign

Resources:

Couldn't connect: Access denied for user 'ninernet_x_site'@'localhost' (using password: YES)