Hi Sean, a few questions I think are missing to complete this proposal, following the structure on the guidelines:

• Is funding happening in one payment? or per milestones?
• What kind of maintenance would the payment functionality need to have after being delivered, if any, taking into account the development of the network? how do you plan to cover this maintenance?
• Why Kusama? I understand the advantages to include customers who prefer paying with crypto and for merchants to expand their markets, however I am hesitant on how this would align with Kusama's vision and roadmap - I just don't know the approach for payment functionality is the right one for a Relay chain token, focusing on speed, scalability and interoperability.

Thanks for the questions,

• The funding is granted at once as the nature of crypto price fluctuation. Granting by milestones also work for us but need to recalc the rate per milestones.
• The payment gateway is developed as the second layer on top of the blockchain, the purpose is to facilitate merchants and devs easily get notifications, history, record, and merchants info during and after payments. Backend Server, API, Dashboard, and E-commerce plugins, Database, receipts management are required dedicated server running continues.
• The nature of blockchain is the ledger and transaction validation but in order to release the potentials, libaries, application layers need to be built in order to help dev building applications.