Assured Credit

Origins (1996) · context: Payment gateway

Assured Credit was established in 1996 as a separate development company so that Assured Card's engineering could stand apart from its consumer business.^[1] Its purpose was to solve the two problems that threatened Assured Card — the cost and the insecurity of a paper, mail-based enrollment — by moving customers onto a secure electronic system: a payment gateway and a terminal through which a payment and a credit application could be taken together over a secure connection.^[9][1]

The on-premise terminal · context: Payment terminal

Assured Credit's on-premise product was the Browser-Based Management Terminal (version 2.0, 1999): a full payment terminal operated entirely through a web browser, pre-installed and configured on the merchant's own hardware, which Dokken describes as the first real web-based payment terminal.^[2] A merchant reached it by installing a packaged Netscape browser; the dashboard ran in the browser with "no IIS plugin required," handling same-day operation.^[2]

It accepted major credit, debit and cheque payments; connected by dial-up modem, leased line, Internet or ISDN; held a customer database with recurring and installment billing; processed in real time or batch; performed split-dial authorization for the major card networks; and ran address, phone and e-mail verification with BIN and card-verification (CVC2/CSC or PIN) checks.^[2]

The hosted gateway and the patent · context: E-commerce

Alongside the on-premise terminal, Assured Credit built a hosted online payment gateway.^[3] Its defining idea was a client-centered model: the payor authorizes a payment through their own financial institution, so the merchant never receives the consumer's banking details.^[3] That invention was set out in the March 2000 patent application "Client-Centered Secure E-Commerce" (CA 2,300,347; PCT WO 2001/067408), assigned to Milinx — an intermediary that holds the consumer's financial and identity data and authorizes payment on their behalf.^[5][6] The application was a published filing that was later abandoned (2003); the 10 March 2000 priority date is its anchor.^[5]

Technology and architecture · context: C++

The terminal and gateway were engineered in C++,^[12] with cross-platform interface work built on Netscape's HTML/Java/JavaScript tooling.^[1] Development and test environments spanned Linux with Novell NetWare and Microsoft Windows NT; the on-premise server stack used NT Server, Microsoft SQL Server, IIS/ASP, Active Directory (LDAP), CryptoAPI, and Java key management (JSSE/KeyStore) with XML routing.^[2][17]

Transport security used SSL, the web-security protocol of the period, with the stronger TLS adopted once it became available in 1999.^[11] The early database layer ran on Microsoft SQL Server; the migration to an Oracle database came later, during the Milinx build, alongside Java/JavaBeans and CORBA middleware.^[18][19]

Into Milinx · context: Software as a service

Assured Credit's mandate was to take both the terminal and the hosted gateway into the application service provider and software-as-a-service model.^[13][14] In 1999 the work merged into the publicly traded Milinx Business Group through its subsidiary Credit Assure Financial; Milinx carried the hosted gateway forward inside its miCommerce suite (miPay, miBilling, miCRM, miStore).^[7][1]

How this related to the development of online payments · context: Financial technology

The patterns Assured Credit built anticipated directions online payments later took — a lineage, not a claim that others used its systems.

• Keeping the consumer's data from the merchant. The client-centered model — the payor's own institution authorizes the payment, so the merchant never sees the banking details — prefigured the data-minimizing, intermediary and tokenized approaches now standard in e-commerce payments.^[5]
• The gateway as a hosted service. Delivering payment acceptance as a hosted gateway rather than merchant-run software prefigured payment-as-a-service, the model later built at scale by companies such as PayPal, Stripe and Adyen.^[9]
• Recurring and real-time billing. Built-in recurring and installment billing with real-time or batch processing anticipated the subscription-billing and real-time transaction systems common today.^[16]

Industry context · context: Payment gateway

Assured Credit worked in the first wave of online payment technology: Authorize.Net and CyberCash were founded in 1994–1996, and Confinity (later PayPal) in 1998.^[9] Against that field, the verifiable, dated anchor for Assured Credit's contribution is the 10 March 2000 patent application for the client-centered gateway model, assigned to Milinx; the "first web-based terminal" framing is Dokken's own and is best read as the browser-operated, on-premise terminal of 1999.^[5][2]

Legacy · context: Financial technology

In summary, Assured Credit is the engineering bridge in the story: it took the problem Assured Card could not solve on paper — serving customers cheaply and securely — and answered it with a browser-based payment terminal and a hosted, client-centered gateway, built in C++ on an SSL-secured stack.^[1][2][11] That work did not stay a private venture: in 1999 it merged into the publicly traded Milinx Business Group, which carried the gateway into its miCommerce suite and filed the client-centered patent that is the dated public record of the idea.^[5][7] The thread runs from SuccessInc's network gateway, through Assured Card's consumer product, to the payment technology here — and on into Milinx.

See also

• Authorize.Net
• CyberCash
• PayPal
• Confinity
• Stripe
• Adyen
• Braintree
• Verifone
• Heartland Payment Systems
• Payment gateway
• Tokenization
• 3-D Secure

References

1. Assured Credit — official site (company history, timeline, gateway). assuredcredit.co.
2. Assured Credit, "On-Premise" — Browser-Based Management Terminal (v2.0, 1999). assuredcredit.co/on-premise.
3. Assured Credit, "Gateway" — hosted online payment gateway. assuredcredit.co.
4. Maynard L. Dokken — official site. maynardldokken.com.
5. Patent CA 2,300,347 A1, "Client-centered secure e-commerce," inventors Dokken, Gifford, Featherstone; assignee Milinx Business Group Inc.; filed 10 March 2000; later abandoned. patents.google.com/patent/CA2300347A1.
6. Patent WO 2001/067408 A1 (PCT family of CA 2,300,347). patents.google.com/patent/WO2001067408A1.
7. U.S. SEC EDGAR — Milinx Business Group, Inc., CIK 0001088815 (Credit Assure Financial subsidiary; 1999 intellectual-property transfer). sec.gov EDGAR.
8. The Wall Street Transcript, biography of Maynard L. Dokken. twst.com/bio/maynard-l-dokken.

9. Investopedia, "Payment Gateway." investopedia.com; also Payment gateway on Wikipedia.
10. Investopedia, "E-commerce." investopedia.com; also E-commerce on Wikipedia.
11. Exabeam, "The Origins of Web Security and the Birth of the SSL Protocol." exabeam.com; also Transport Layer Security (SSL/TLS) on Wikipedia.
12. ISO C++ (Standard C++ Foundation). isocpp.org; also C++ on Wikipedia.
13. TechTarget, "application service provider (ASP)." techtarget.com; also Application service provider on Wikipedia.
14. TechTarget, "software as a service (SaaS)." techtarget.com; also Software as a service on Wikipedia.
15. National Institute of Standards and Technology, The NIST Definition of Cloud Computing (SP 800-145). csrc.nist.gov; also Cloud computing on Wikipedia.
16. IBM, "What is online transactional processing (OLTP)?" ibm.com; also Online transaction processing on Wikipedia.
17. Microsoft Learn, "SQL Server documentation." learn.microsoft.com; also Microsoft SQL Server on Wikipedia.
18. Oracle, "What Is a Database?" oracle.com; also Oracle Database on Wikipedia.
19. Oracle, "Java." oracle.com/java; also Java on Wikipedia.
20. Windows NT — Wikipedia; and Novell NetWare — Wikipedia.
21. Netscape — Wikipedia.
22. Tokenization (data security) — Wikipedia.
23. CORBA — Wikipedia.