GraphQL API Stack for Flexible Digital Token Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy APIs of online transaction processors are not compatible with the coding and query languages used by service providers, leading to inefficient interactions and increased computing and network resource usage when processing digital payment tokens.
Innovation Solution
Implementing GraphQL API stacks for API interoperability, allowing for flexible digital tokens that reduce data field queries and enable efficient data processing by using GraphQL as a query and manipulation language for exchanging API calls and requests between transaction processors and service providers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If legacy APIs are used for interaction between service providers and transaction processors, then system compatibility is maintained, but API interoperability deteriorates due to language incompatibility
Solution Approach 1:
The patent introduces an intermediary layer that translates between GraphQL queries from service providers and legacy API calls to transaction processors. This mediator enables interoperability between different API languages without requiring direct compatibility, resolving the contradiction by allowing GraphQL and legacy APIs to coexist and communicate through translation.
Solution Approach 2:
The system changes the parameter format of API calls from traditional REST/JSON to GraphQL query syntax. By transforming the request parameters and data structures to match GraphQL's schema-based approach, the system achieves interoperability while maintaining backend legacy system compatibility.
2Productivity
If multiple API calls are made to exchange and process digital payment tokens, then data processing completeness is improved, but computing and network resource usage increases
Solution Approach 1:
The patent segments data requests into specific GraphQL fields that can be precisely selected. Instead of fetching entire datasets through multiple API calls, the system divides data into granular fields and only retrieves what is needed, reducing unnecessary network traffic and processing overhead while maintaining complete data processing capability.
Solution Approach 2:
The system implements partial action by allowing clients to request only the specific fields they need through GraphQL queries. This selective data retrieval approach reduces the volume of data transferred and processed compared to traditional API calls that often return complete datasets, thereby reducing computing and network resource consumption.
3Speed
If traditional REST APIs are used for data exchange, then system simplicity is maintained, but data processing speed deteriorates due to excessive data fields
Solution Approach 1:
The patent extracts and removes unnecessary data fields from the data exchange process. By using GraphQL's schema-based querying, the system allows clients to specify exactly which fields are needed, extracting only the essential data from the entire dataset. This reduces the amount of data transmitted and processed, thereby increasing processing speed while the GraphQL framework handles the complexity of field selection.
Data Source
AI summary
There are provided systems and methods for flexible digital tokens with application programming interfaces for reduced computing calls. A service provider, such as an electronic transaction processor for digital transactions, may provide a processing system, stack and API that allows for generation of flexible payment tokens that can be used for electronic transaction processing with external service providers including social networking platforms and services. The processing system for the transaction processor may include an API in a compatible language with the APIs of the external service providers. Specific API calls and queries, which may correspond to GraphQL mutations, may be used to execute operations between the APIs of the interfacing systems to have a legacy processing system and API to generate a billing agreement. Once generated, the billing agreement may be tokenized, and a payment token used for payment processing.