Dynamic Payment Data Push to PSP via Merchant Portal

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current payment transaction systems require cumbersome infrastructure changes and manual entry of specific codes to register Payment Service Providers (PSPs), leading to delayed payment processing and a poor end-user experience, especially when multiple PSPs need to be registered or when merchants want to dynamically select PSPs during transactions.

Innovation Solution

A server system within a payment network receives a payment transaction request with a PSP ID, fetches the corresponding URL from a merchant portal database, and automatically sends the payment transaction data to the PSP server for processing, eliminating the need for manual code entry and infrastructure changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual entry of PSP codes and infrastructure changes are implemented to register Payment Service Providers, then the system can process payment transactions through multiple PSPs, but the deployment process becomes cumbersome and transaction processing time increases

Engineering Contradiction:

Improveability to process transactions through multiple PSPsVSAvoidtransaction processing time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-registering PSPs with the payment network before actual transactions occur. The merchant portal allows merchants to register multiple PSPs in advance, and the wallet server stores PSP identification information and endpoint URLs in a database. This preliminary setup eliminates the need for manual code entry and infrastructure changes during actual transactions, enabling fast dynamic selection and pushing of payment data to the chosen PSP.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If manual code entry and infrastructure changes are required to register PSPs, then the system can establish communication with PSPs, but the deployment process becomes complex and time-consuming

Engineering Contradiction:

Improvecommunication establishment with PSPsVSAvoiddeployment complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service mechanisms where the wallet server automatically manages PSP communication. The wallet server dynamically selects the appropriate PSP based on transaction context and automatically pushes payment transaction data to the selected PSP's endpoint without requiring manual intervention. The merchant portal automatically registers PSPs and stores their identification information, eliminating the need for manual code entry and reducing deployment complexity while maintaining reliable communication.

Inventive Principle:

Principle #25Self-service

3Productivity

If the wallet application requests payment transaction data from the PSP, then the PSP can process the transaction, but the communication process becomes multi-step and slower

Engineering Contradiction:

Improvetransaction processing speedVSAvoidcommunication process simplicity

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

The system inverts the traditional communication flow by having the wallet server push payment transaction data to the PSP instead of the PSP requesting data from the wallet application. The wallet server dynamically selects the PSP and initiates the data transmission to the PSP's endpoint. This inversion reduces communication steps, eliminates the need for the PSP to query for transaction data, and accelerates the overall transaction processing speed while maintaining operational simplicity.

Inventive Principle:

Principle #13The other way round (Inversion)

Data Source

PatentUS11507936B2Payment transaction systems and methods by dynamically pushing data to payment service provider

Publication Date: 2022.11.22 MASTERCARD INT INC

AI summary

Embodiments provide payment transaction methods, and systems by dynamically pushing payment transaction data to a Payment Service Provider (PSP). Method includes receiving, by a server system associated with a payment network, a payment transaction request including a payment transaction data and a PSP identifier (ID) of PSP during a payment transaction initiated from a user device using a merchant application. The method includes fetching, by the server system, a corresponding Uniform Resource Locator (URL) of the PSP using the PSP ID of the PSP from a merchant portal database. The merchant portal database at least includes a list of one or more URLs stored against respective one or more PSP IDs pre-generated based on linking respective one or more PSPs to a merchant profile. The method includes sending, by the server system, the payment transaction data to a PSP server using the corresponding URL for processing the payment transaction.