Skip to main content

Functionalities

Learn how DePay's payment protocol functions in detail.

In order to simplify integrations, DePay provides the web3-payments JavaScript SDK.

Pay​

The DePay payment protocol primarily facilitates payment transactions. It accepts all essential payment details, executes the payment, and, if necessary, converts tokens. Additionally, it has the capability to deduct a transaction fee before transferring the final amount to the recipient.

EVM​

The pay function can be executed with prior token approvals granted by the payment sender or with a Permit2 SignatureTransfer.

The pay function takes a payment tuple as input with the following structure:

  {
    amountIn: "1000000000000000000",
    paymentAmount: "970000000000000000",
    feeAmount: "1000000000000000",
    feeAmount2: "1000000000000000",
    protocolAmount: "1000000000000000",
    deadline: 1749050994536,
    tokenInAddress: "0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE",
    exchangeAddress: "0x3fc91a3afd70395cd496c647d5a6cc9d4b2b7fad",
    tokenOutAddress: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
    paymentReceiverAddress: "0x4e260bB2b25EC6F3A59B478fCDe5eD5B8D783B02",
    feeReceiverAddress: "0x9Db58B260EfAa2d6a94bEb7E219d073dF51cc7Bb",
    feeReceiverAddress2: "0x9Db58B260EfAa2d6a94bEb7E219d073dF51cc7Bb",
    exchangeType: 2,
    receiverType: 0,
    exchangeCallData: "0x24856bc30000000000000000000000000000000000000000000000000000000000000040000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000020b000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000040000000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000016aecd87787024340000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000016aecd877870243400000000000000000000000000000000000000000000000000000000000f424000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002b0d500b1d8e8ef31e21c99d1db9a6444d3adf12700001f4c2132d05d31c914a87c6611c10748aeb04b58e8f000000000000000000000000000000000000000000",
    receiverCallData: "0x0000000000000000000000000000000000000000",
  }

amountIn: The amount paid into the router from the msg.sender.

paymentAmount: The amount paid to te payment receiver.

feeAmount: The amount paid to the fee receiver.

feeAmount2: The amount paid to the second fee receiver.

protocolAmount: The amount paid to the protocol.

tokenInAddress: The address of the token paid into the router from the msg.sender. Use 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE for the native token of the respective blockchain.

exchangeAddress: The address of the exchange to use in order to convert the incoming token into the outgoing token. The exchange address needs to be enabled by the protocol governance first.

tokenOutAddress: The address of the token paid out to the payment receiver and optionally to the fee receiver.

paymentReceiverAddress: The address of the receiver of the payment.

feeReceiverAddress: The address of the fee receiver.

feeReceiverAddress2: The address of the second fee receiver.

exchangeType: The type of the exchange.

  • 0 just exchange; e.g. WETH/ETH
  • 1 pull; The exchange will pull the token into the exchange router; Approval required; e.g. Uniswap V2
  • 2 push; The exchange expects the token to be pushed into the exchange router; e.g. Uniswap V3

receiverType: The type of the receiver.

  • 0 just send; tokenOut will be transfered to the receiver address.
  • 1 receiver will pull; tokenOut approval will allow the receiver contract to pull the tokens out of the payment router; not suitable for the native token of a blockchain (use push instead)
  • 2 push to receiver; tokenOut will be pushed to the receiver contract as part or prior to calling the given call data of the receiving smart contract.

exchangeCallData: The call data applied to the exchange address in order to convert token in to token out.

receiverCallData: The call data used to call the receiving smart contract.

deadline: unix timestamp (ms) after which the payment will be declined by the smart contract.