Introduce Alternative Payment Link Syntax

Ideas
1

I’m not sure if below is something you can change or is part of global standard.
Currently, the payment link used for sending/receiving funds in TrustWallet has the following syntax:

domain:address[?params]

Examples:

bnb:bnb1ultyhpw2p2ktvr68swz56570lgj2rdsadq3ym2?amount=1.23456&memo=S0032415
binance gbp stable coin:bnb1ultyhpw2p2ktvr68swz56570lgj2rdsadq3ym2?amount=1.23456&memo=S0032415

None of above contain information about platform (‘bitcoin’, ‘bep2’, ‘erc20’ etc.). Some links use currency symbols and others their verbal names what makes it pretty frustrating to generate them automatically in the application. Spaces in currency name are even more troublesome especially for apps parsing links automatically.

IDEA:
I suggest to introduce the following syntax (optional components in square brackets):

platform:[symbol@]address[?params]

where:
‘platform’ is specified as (‘bitcoin’, ‘bep2’, ‘erc20’ etc.)
‘symbol’ is a currency symbol (or original symbol) unique within given platform, e.g. ‘BNB’ or ‘BGBP’ (or ‘BGBP-CF3’). This component could be omitted when using single currency platform like ‘bitcoin’ or when creating general transfer link for any currency running on given platform.
Examples:

bitcoin:1KFHE7w8BhaENAswwryaoccDb6qcT6DbYY?amount=0.123456
bep2:BGBP@bnb1ultyhpw2p2ktvr68swz56570lgj2rdsadq3ym2?amount=1.23456&memo=S0032415
erc20:BGBP@0x3f5ce5fbfe3e9af3971dd833d26ba9b5c936f0be?amount=1234.56

Furthermore it would be easier to specify which wallet application should handle requests for which platform e.g. ‘bitcoin:’ would open standard BTC wallet and ‘bep2:’ or ‘erc20’ would open TrustWallet.

2 Likes
2

Currenty you can do:

bitcoin:1KFHE7w8BhaENAswwryaoccDb6qcT6DbYY?amount=0.123456
ethereum: 0x3f5ce5fbfe3e9af3971dd833d26ba9b5c936f0be?amount=0.123456

Checkout Deep Linking for sending payments: https://developer.trustwallet.com/deeplinking#send-payment

But we gonna introduce a way to specify a way to send token to as(in about 2 weeks)

ethereum:0x3f5ce5fbfe3e9af3971dd833d26ba9b5c936f0be?token=0x123..123&amount=0.123456
bnb: bnb1ultyhpw2p2ktvr68swz56570lgj2rdsadq3ym2?token=BGBP-BGO&amount=0.123456&memo=123
2 Likes
3

I’m guessing for now this is the only source they trust with their transactions without loop holes

4

Is there ETA for payment link syntax changes you described?

2 Likes