Payment Intents
You decide what you want and we deal with the execution
Last updated
You decide what you want and we deal with the execution
Last updated
Intent based architecture allows us decoupling from the usual ways of how we do transactions on Web3 and lets us create a better user interface.
Intents are partial transactions that are not created yet. They represent pure user intention or user operations that can be used to build a transaction in the future.
At DebitLlama we deal with payment intents only, they represent the intention to make recurring payments to an address for a period and interval. The payment intents can't be modified and can be converted into transactions that can only succeed if all the conditions are met.
You can cancel your payment intents any time directly or by disconnecting the wallet
DebitLlama subscription payments are secure by default. The full wallet balance is never exposed and all payments contain a maximum limit.
When connecting a wallet and approving a payment, you let us know you wish to start making payments and we handle the rest. It's that easy.
To create a payment intent, there must be an item that is purchased. This is represented by a debit item, which defines the parameters of the subscriptions. Debit Items are created by the merchants and link to a custom checkout page which can be used to create payment intents related to that item.
Intents are initially saved with Created status. After the first payment is made the status is changed immediately. Paid status represents a payment intent that finished, Recurring means there are pending future payments that are currently not fulfill-able.
There are error states which correspond to Relayer balance too low or Account balance too low. The relayer balance must be topped up by the merchant to pay for the transactions, else the payments will not fulfill. This doesn't have to be done in all cases, if the transaction fees can be covered by protocol fees, the relayer fee can be avoided. Account balance too low is an error when the payment intent creator, the customer can't make payments. The error will persist until the balance is refreshed after a deposit.
This pricing represents the mechanism of how the payments are made. When a payment intent is created with fixed pricing it will auto fulfill. The payment amount is withdrawn immediately and will repeat with the interval until the subscription ends. These subscriptions cost the same amount each time and the total payments can be determined at the start
This pricing allows pay as you go payments and lets a merchant request a payment amount.
The payment intent contains a max debit-able amount that was approved per payment for the length of the subscription, but the final price is determined by the merchant who must create a Dynamic Payment Request with the actual amount that will be debited. These requests must be made by the merchant on the Payment Intent's page manually or via the API. When the request is created, the payment intent automatically fulfills if the required account balance is sufficient
