How to Claim USDT for STRIPE transaction

Claim Process

The settlement of Stripe payment revenue follows the policy here.

  1. Retrieve an information for creating transaction for the claim from the Dapp Portal.

  2. Sign the transaction using the address currently receiving Kaia-based settlements.

  3. Broadcast signed transaction.

    1. If fee delegation is enabled, transfer the signed transaction to the Fee Payer Server.

    2. If fee delegation is not used, broadcast the signed transaction directly to a Kaia node.

API to retrieve information to create unsigned transaction

Request API to receive STRIPE payment revenue in USDT

API Path

get /api/b2b-v1/dapp-settlements/{client_id}/signed-receivable

Domain

https://api.dappportal.io

Path

/api/b2b-v1/dapp-settlements/{client_id}/signed-receivable

Authentication Information

This API requires Dapp Portal authentication.

Please include the following information in the request headers for authentication

Name
Description

client_id *required string (path)

Client identifier string (36 bytes) obtained from support team

X-Auth-Client-Id *required string (header)

Client identifier string (36 bytes) obtained from support team

X-Auth-Timestamp *required string (header)

Current time in Unix epoch format

X-Auth-Salt *required string (header)

Randomly generated UUID string (36 bytes)

X-Auth-Signature *required string (header)

(*) HMAC-based signature proving request authenticity

(*) base64encode(hmac("{clientId}|GET|/api/b2b-v1/dapp-settlements/{clientId}/signed-receivable|{timestamp}|{salt}"))

Response

field
type
description
example

transaction

  • to

String

contract address to call

"0xdce5..."

  • value

String

native token's amount to send

"0x0"

  • data

String

data of smart contract

"0x...."

Sample Code

Retrieve transaction executing load() function from Dapp Portal

Create and Sign Transaction

  1. Create transaction with response from Dapp Portal.

    1. to, value, data

  2. Sign the transaction using the address currently receiving Kaia-based settlements.

  3. Broadcast signed transaction.

    1. If fee delegation is enabled, transfer the signed transaction to the Fee Payer Server.

      1. Path: /api/signAsFeePayer

      2. POST (application/json) { userSignedTx: {rawSignedTx} }

      3. Add type: 49 while creating transaction to use fee delegation

    2. If fee delegation is not used, broadcast the signed transaction directly to a Kaia node.

Sample Code

⚠️ This sample code applies to cases where the Kaia Wallet (Web Extension) is used.

If you choose to sign the unsigned transaction (obtained via API) using a different method, please make sure to use the signing method appropriate for your chosen approach.

Complete Example: From Claim to Broadcast

⚠️ The example code provided is for illustrative purposes only. You should review and modify it appropriately to ensure it fits securely within your production environment. We do not take any responsibility for issues or damages caused by using this code as-is.

Last updated