PumaPay has developed an advanced billing infrastructure for merchants, allowing them to design flexible payment schemes through the blockchain. PumaPay's open source payment protocol is a pioneering blockchain solution that provides a powerful payment mechanism that is more reliable, efficient, flexible, economical, and scalable than traditional implementations (credit cards). Unlike today's payment methods, which include credit cards and virtual coins like Bitcoin, the Pull Payments protocol is designed to overcome real barriers and provide a set of tools to provide businesses and individuals with a smooth login process. The PMA token is the primary facilitator and means of value transfer within the PumaPay ecosystem.

Project Vision

The PumaPay open source withdrawal payment protocol is a comprehensive blockchain solution that provides a robust payment mechanism that is more reliable, efficient, flexible, cost-effective and scalable than current implementations (credit cards). Unlike today's payment methods, which include credit cards and virtual currencies such as Bitcoin, the Withdraw Payment protocol has been designed from the ground up to overcome existing barriers and provide a set of development tools to facilitate the onboarding process for businesses and individuals.
Using PumaPay, merchants can:
plug in various billing solutions to accept cryptocurrencies directly, replacing redundant banking layers;
provide customers with a comprehensive and flexible billing solution that addresses All common billing processes, including recurring payments, pay-per-use, etc.;
eliminates the risk of fraud and chargebacks and associated fines;
saves expensive middleman transaction fees, currently from about 3% to as high as 15%.

Project Highlights

PumaPay tokens are "facilitators" of unique features of the protocol. It is the only way to transfer money between parties through the protocol, convertible from any other cryptocurrency or fiat currency. We will promote the adoption of PumaPay tokens in online and offline industries, while focusing on e-commerce and online services. By facilitating the integration of our protocol and making PMA the de-facto payment method, we intend to gain a large number of users and thus build a thriving cryptocurrency economy.

Our token economy is based on four pillars:
Early Adopters
Businesses from various industries who have committed to PumaPay withdrawal solutions.

Launch Partners
Our Launch Partners integrated the PumaPay withdrawal payment protocol into their platform and worked closely with us to lay the foundation for decentralization across the industry through widespread adoption of the PumaPay token .

PumaPay Pride
Wallet-integrated application where PumaPay token holders can search for places to pay for tokens, greatly increasing the attractiveness of participating businesses.

Third-party complementary service providers
enable third-party companies to create a service layer on top of the protocol, contributing to the PumaPay ecosystem, thereby creating new business opportunities for enterprises (eg trust network, security, code verification, etc.).

Application scenario

1. Fixed amount recurring payments
Bob is passionate about cryptography and security. Therefore, he hopes to subscribe to National Cryptographic, a world-renowned journal in the field of global security and blockchain. Since the National Cryptographic website uses PumaPay, Bob can easily order.
First, Bob can view the order and use his PumaPay wallet to scan the QR code for payment.
After scanning the QR code, a YAML file will appear on his wallet stating the terms of the PullContract and any details about the PullContract.
Once Bob accepts, the PullContract is submitted to the blockchain, Bob subscribes to National Cryptographic, and National Cryptographic has the right to operate PullRequests from Bob's account every month.

2. Pay-per-view
John is a nutritionist who provides real-time consulting services through the Internet. He uses PumaPay to provide services.
Pre-determined PumaPay token deposit amount will be obtained via PullContract sent by John to his client using a QR code before the session starts.
After the client accepts the PullContract, John can start the session.
During the entire session, use PullContract to record the time used; using the transaction status channel protocol, the platform should confirm every 15 seconds whether the session is still valid and whether the customer has enough PumaPay tokens.
When the session ends, the smart contract will transfer to the business the portion consumed from the earned amount, and any remaining portion will be automatically returned to the customer account.

3. Regular payments at fixed times
Sarah just bought her first house and now has some bills to pay. She looked at her electric bill and discovered that her utility had accepted PumaPay. She goes to the website and enters her account information. When choosing a payment method, she chose PumaPay.
During this process, the utility company's webApp creates a PullContract using the PumaPay SDK.
A QR code linking to the PullContract is generated and displayed to Sarah.
Sarah can scan this QR code and get the details of the contract, which states that the utility company may withdraw a variable amount from her account each month, depending on her electricity consumption.
Sarah knows that her electricity bill will never exceed $100, so she uses her wallet to set a real-time equivalent limit of $100 in Puma via PullContract.
Sarah accepts the PullContract, which is stored in the token contract, and Sarah will be connected to the grid.

4. One-time/single payment
Lily and Sam are going on a date. Beforehand, Sam checks PumaPay Pride restaurants online to see a list of nearby restaurants that accept PumaPay.
Lily and Sam decide to have dinner at a fancy Ethiopian restaurant around the corner from Lily's apartment. After a delicious dinner, the waiter brought the bill. Sam decides to use PumaPay to pay for dinner. The bill included a QR code, which Sam turned on his phone and scanned into his PumaPay wallet.
After scanning the QR code, the wallet will display the transaction details. When Sam agrees to the transaction, the PullContract will be submitted to the blockchain, and the restaurant will (via the SDK component implemented in the POS system) submit a PullRequest to Sam's account.

5. Shared Payments
David has a fairly successful online store that he wants to expand. He knows the advantages of affiliate marketing and wants to take advantage of them. Since he doesn't have the resources to build a reputable affiliate network, it's hard for affiliates to trust him to pay commissions on time. If he submits an offer to an existing affiliate network, it will cost him unnecessary intermediate fees. With PumaPay, David can create a PullContract to charge his customers and link it to a split payment contract that automatically splits the revenue between each of his accounts and affiliates. This ensures that both the Union and David get their fair share of each immediately without any risk, solving the trust issue.

6. Restricted payments
Timmy is a little boy, he is in elementary school, and his mother wants to give him money for lunch, but she doesn't want him to spend it on candy. By using third-party restrictions, PumaPay can allow his mom to monitor his connected wallet activity and ensure Timmy's money is spent in the right place. If Timmy tries to buy candy, his request will be submitted to his mom's wallet, and the transaction will be approved if it meets certain predetermined parameters set by his mom, and not if it doesn't. When Timmy tries to make a purchase, he will receive a sad face if the payment is not approved, and a smiley face if approved. In this use case, Timmy's mom has set purchase parameters to approve or deny transactions in real time; effectively enforcing parental controls on Timmy's purchases even when his mom is away. This use case could also be achieved by using a pop-up approval message on the device, requiring Mommy Timmy to manually approve each purchase. This real-time message can pass through the party creating the limiter, but the message itself will be done off-chain. It's important to note that this is a simple use case that limits the number (velocity) of transactions, type of business, etc. Also, there can be many other setups, but these two use cases demonstrate the ease of control Timmy's mom has over his consumption.

Related links:
https://www.qukuaiwang.com.cn/szhb/3216.html###