ERC20 Paymaster
Available on ZKsync Era mainnet, ZKsync Sepolia, Cronos zkEVM Mainnet, Cronos zkEVM Tesnet, Abstract Tesnet.
Last updated
Available on ZKsync Era mainnet, ZKsync Sepolia, Cronos zkEVM Mainnet, Cronos zkEVM Tesnet, Abstract Tesnet.
Last updated
This guide will help you get started with the Zyfi API to transform a normal transaction in a paymaster one.
For advanced usage and detailed explanation of each parameter and feature, please explore our detailed .
The basic flow consists of the following steps:
Collect the desired transaction payload and the ERC20 the user desires to pay with
Send an API request
Receive back the quote and transaction payload for the user to sign
Send the required data to the erc20_paymaster
endpoint. Below an example implementation using Javascript (natively supported in most environments)
The returned object does not change the original transaction calldata, but add the paymaster fields necessary to process the transaction.
The response, on top of the transaction payload, returns a series of helper values that can be used by the UI to better inform the user. In particular:
tokenAddress
: ERC20 token address used to pay for the gas fee (feeToken)
tokenPrice
: the estimated cost of the feeToken
feeTokenAmount
: Max amount of the ERC20 token that the user will pay as fee (before refunds). The user need to have this balance for the transaction to not fail
feeUSD
: Equivalent value of feeTokenAmount in USD
markup
: Markup or discount applied on the gas fee
expirationTime
: block.timestamp
of the quote expiration. Currently it's one hour
Below an example implementation with
Ensure you are using V5 or V6.
Make sure to check to enable zkSync specific features