Need a billing platform that checks local tables to determine if account is serviceable; then posts to third party service to determine if 1) address and info is valid; 2) Security codes are valid (two different processes, one then the other); Then Submits Record for billing.
We then need a recurring billing module made. Accounts are billed monthly on statement date, this means daily a service would run that submits a post (1 per account/transaction) for accounts that are automatically renewed.
For our CRM (customer manager)
We would need an account search feature (by phone number for instance)
It would search for active accounts that have been billed, and open accordingly matches
On the page it will show customer information (name, address, ip, etc)
It will give an option to cancel/deactivate account
It will need to be planned to allow addons, such as the ability to process refunds, search bill history, etc.? ? ? ?
## Deliverables
Data will be sent to pagescript that:
Captures and Writes data received to local database
Checks local validation rules
If passes send to ThirdPartyValidatorA
CapturesResponse from ThirdPartyValidatorA
If passes send to ThirdPartyValidatorB
Captures Response from TPV-b
If passes, send record to ThirdPartySale (ie, submit the transaction)
Record response from ThirdPartySale script (such as transaction ids, etc)
Once complete, our page/script will display a PASS or FAIL response back to person sending data to us.
Script/job is scheduled to run daily that will check to see if there are any "renewals" that need to be submitted. A ruleset will be created to handle specific registration dates. For instance
On the 1st, it will select all records older than 20 days whos RegistrationTime DAY falls on 29,30,31,1? for renewal. On 2nd it will renew all accounts with RegistrationTime DAY of 2 that are older than 20 days.
A CRM will need to be written that cosists of:
1) an administrator login
? 2) Admin page that allows creation of usernames/pw
3) A user login page
4) Account search page
5) Customer Details page - this includes options to Cancel the account (when any action is taken on account, it would record the Username of person who did it, date, and action taken in a "notes" table - this would also be displayed on the Customer Details Page
This platform would eventually need to be able to process text files to track billing histories, rejected transactions, etc. However the basics is needed first.
All third party submissions for