Regarding payment collection #156
pkapustin
started this conversation in
Core Specification
Replies: 2 comments 1 reply
-
|
I agree with all the reasons mentioned above. But should this be a network level decision or should this be a part of the core protocol specifications itself? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I think it should apply to all networks: BAPs and BPPs have to act according to their roles. BAPs are customer-facing platforms that make the services available to the customer and combine them. BPPs provide those services. This basic premise has to hold for the network to be able to grow and provide value for the customers. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We had a discussion on payment collection by BAP vs BPP. The summary is that BAP has to collect. Here are some of the main reasons.
Composability
The customer can only checkout once, and the price may consist of several parts.
Examples:
There are plenty of examples like this from all domains (multi-leg trips, insurance, additional services, etc.)
If we were to implement a BPP integration in a way where the payment is collected by the BPP, it would have these consequences:
This would essentially prevent many new BAPs from joining the network, as it is essential for their business to compose several services, add their own services and collect extra fees.
Uniform interface
The flows have to be the same in the same network / domain. We cannot have different types of payment collection as this would require different flows (as notifications from payment gateway would come to different parties).
User experience
Payment collection by BAP is essential for good and consistent user experience. For this, the following is needed:
BAP and BPP have totally different roles. Here is one analogy: BAP is like a software application, BPP is like a library / service that are used in an application. One application can use many services / libraries. It is only the application that can display UI.
It should be noted though that BPPs need to be educated about this, so that it is explained clearly why it has to be the BAP that collects the payments.
Beta Was this translation helpful? Give feedback.
All reactions