Payment Token for Secure SaaS Billing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the context of Software as a Service (SaaS) and pay-as-you-go models, existing payment and accounting processes lack security and reliability, particularly in provisioning and processing payments for computing services.
Innovation Solution
The creation and use of secure payment authorization tokens, which are encrypted and combine customer and service provider parameters, using a method involving data buffers signed with private and public keys to ensure secure and reliable transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional payment processing methods are used in SaaS models, then payment processing can be performed, but security and reliability are compromised
Solution Approach 1:
The patent introduces a payment token as an intermediary object that mediates between the customer and service provider. This token contains encrypted payment information and enables secure transactions without exposing sensitive data, thereby resolving the security reliability contradiction in SaaS payment processing
Solution Approach 2:
The patent transforms payment data into a tokenized format with changed parameters - the original payment credentials are encrypted and replaced with a token that contains hashed and salted information. This parameter transformation ensures that even if the token is intercepted, the original payment data remains secure, addressing the security concerns in cloud-based payment systems
2Reliability
If payment tokens are encrypted with multiple keys, then security is enhanced, but system complexity increases
Solution Approach 1:
The patent segments the encryption process into distinct components: customer public key encryption for the token body, customer private key for signature, service provider public key for verification, and service provider private key for token creation. This segmentation allows each party to manage their own keys independently while maintaining overall security, reducing the complexity of multi-key management
Solution Approach 2:
The patent implements preliminary actions by pre-establishing public key pairs for both customer and service provider before transactions occur. The service provider pre-stores the customer's public key and pre-computes hash salts, enabling secure token creation and verification without requiring complex real-time key exchange, thus simplifying the overall system operation
3Measurement precision
If multiple data records are combined into a token, then payment accuracy is improved, but processing time increases
Solution Approach 1:
The patent merges multiple data records (customer information, service provider information, payment details) into a single consolidated token structure. This combining approach ensures payment accuracy by integrating all necessary verification data in one secure object, while the efficient merging process minimizes processing time compared to handling separate records
Solution Approach 2:
The patent changes the parameter structure of payment data by transforming multiple separate records into a token with a specific hierarchical structure containing encrypted fields. This parameter transformation allows for efficient processing by organizing data in an optimized format that balances completeness with processing speed
Data Source
AI summary
Examples implementations relate to payment tokens. An example includes a customer computer creating a first data buffer, with a set of customer-specified parameters, signing the first data buffer with a customer private key, associating a customer public key to the signed first data buffer to create a first data record that is communicated to a service provider. The service provider computer creates a second data buffer with a set of service provider-specified parameters, signs the second data buffer with a first private key of the service provider, associates a first public key of the service provider to the signed second data buffer to create a second data record, combines the first and second data records, signs the combined data record with a second private key of the service provider, and associates a second public key of the service provider to the combined data record.