Re: Add new capabilities to Payment Architecture Priorities

On 05/28/2015 10:20 AM, ËïÙ»(Ñ©µÏ) wrote:
> We have added 4 new capabilities for the ¡°Payment Architecture 
> Priorities¡±, which are qrcode payments, payment under guarantee , 
> risk monitoring and provisions transferring, please review them.

Hi ËïÙ» and ¶Î³¬,

I have reviewed the new capabilities and have a few questions:

------------------------

I understand QRCode payments as a general feature, but don't understand
these requirements, could you elaborate, please?

> l   Data encoding and encryption for invoices

Why do you need an encrypted invoice via QRCode?

> l   Generate qrcode with client characteristic data

What does "client characteristic data" mean?

------------------------

I don't understand what "payment under guarantee" means. Could you
please elaborate with a use case?

> l   Storage of payment¡¯s status(include placed an order, paid to 
> Payment Agent, received products or services, paid to merchant)

Where is the payment's status stored?

> Protocol for transmitting between payer and payment agent, payment 
> agent and merchant

What is transmitted, the status of the payment? Or something else?

> l   Handling dispute in the process

What are the kinds of disputes that need to be handled?

> l   Storage of payer¡¯s private information

Where are the payer's private information stored?

------------------------

> risk monitoring

Which actors / roles do the risk monitoring?

The payers, payees, or account providers?

> l   Risk monitoring rules according to different transaction types

Can you provide a number of examples of the types of rules that can be
used based on the transaction types?

> l   Recognizing risky transactions by monitoring rules

Elaborate more, please.

> l   Alert about risk through email, sms, etc

Where are the alert preferences kept? Are they in a standard format
along with the rules? Does this need to be standardized?

---------------------

> provisions transferring
	
I don't understand what "provisions transferring" means.

> l   The bank transaction fund settlement to payment agent¡¯s account

I don't understand this, could you elaborate? Is this the movement of
funds from the payer to the payee? Or is this the movement of funds from
the payer to an escrow account?

> l   payment agent¡¯s account fund settlement to merchants¡¯ bank
> account

Is this the movement of funds from an escrow account to a payee?

If you could provide a few new use cases, I think that would help me
understand the sorts of capabilities you'd like to see as well as where
they fit into the payment phases.

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: Web Payments: The Architect, the Sage, and the Moral Voice
https://manu.sporny.org/2015/payments-collaboration/

Received on Friday, 29 May 2015 02:23:51 UTC