The core of pull payments lies in the payment request. This request is essentially a list of transactions approved by the receiver and sent to the sender (or initiator). Let’s understand it like this: Pull payments operate like a digital version of sending a bill. Think of it like receiving an online invoice. The receiver creates an invoice (payment request) detailing the amount for specific items (token transfers).

This digital invoice supports various systems, be it EVM or non-EVM blockchains, and can recognize addresses and protocols like ENS, SOL, APT, UNSTOPPABLE, etc. (Powered by Fetcch’s Identity Layer) The sender then gets the invoice, reviews it, and approves the payment. It's a straightforward and efficient way to handle transactions.

These transaction Requests can either be simple payments or can also execute a complex multistep transaction.

They will be completely blockchain agnostic and enable payment gateways, point-of-sale systems, or any commerce platform to start accepting guaranteed crypto payments with very little integration. It can also be used by dApps to execute transactions without directly connecting to a wallet, so any dApp that can only be used for a single transaction can reduce the complexity of connecting to a wallet.

As transaction requests are transmitted over HTTPS, we have a 100% guarantee that all network packets will be received by the end-user, we can also improve the current mobile wallets to a desktop dApp experience. dApps can directly send transaction requests to a mobile-based wallet, it can execute that transaction and dApps will be notified that the transaction is completed, so there is no overhead of a websocket connection dropping off.

Last updated