Warning:
This wiki has been archived and is now read-only.
Payment Agent Contributions
From Web Commerce Interest Group
WARNING: This is a staging area for contributions to be evaluated by the task force. It is not predictive of the direction of the group.
Description
This page contains models, descriptions, and other artifacts to be brought under discussion of the Payment Agent Task Force.
Agent Environment
A diagram that places the Payment Agent relationships with the other active shopping agents.
Error creating thumbnail: Unable to save thumbnail to destination
- Shopping Terminal and Payment Terminal could be (and often ore) the same terminal. But the 'out-of-Band' type of payment is one of those that require a specific attention on the communication between the shopping browser agent and the external Payment Agent for discovery listing and secure data exchange.
- Account push or pull mechanism defines the payment proof flow and security level to be applied on the exchanged data.
Payment Flows
Data flow diagram that describes the various possible data exchange between the Payment Agent and others shopping agents.
Error creating thumbnail: Unable to save thumbnail to destination
- The Payment Agent has several roles: Discovery of the available payment means, Payment processing (authorization and settlement), Payment history.
- The Payment Agent verifies the user/payer credentials versus the payment means/scheme authorization and handles the generated proof or deny of payment.
- The Payment ticket is data set that contains the merchant's and payer's id, the payment object reference and details (amount, currency, etc.) and the payment proof.
- Payment authorization and capture may be the same operation.
- Payment proof may be forwarded for settlement to the relevant payment processor by the user payment agent (directly or via a gateway) or the by merchant (directly or via a gateway).