One of the core features that almost every existing Obyte chatbot has is sending and receiving payments. This enables bot developers immediately add payment to the service they could be providing with
Requesting payments
When you include a valid Obyte address anywhere in the text of your response to the user, the address will be automatically highlighted in the user's chat window, and after clicking it the user will be able to pay arbitrary amount of arbitrary asset to this address.
When you want to request a specific amount of a specific asset, format your payment request this way:
1
Any text before [payment description, will be ignored](obyte:ACCOUNT_ADDRESS?amount=123000&asset=base) any text after
Copied!
Example:
​
Amount is in the smallest units, such as bytes. If you omit &asset=... part, base asset (bytes) is assumed. If you want to request payment in another asset, indicate its identifier such as oj8yEksX9Ubq7lLc+p6F2uyHUuynugeVq4+ikT67X6E= for blackbytes (don't forget to url-encode it).
You will likely want to generate a unique payment address per user, per transaction. This code sample might help:
It is possible to request that the payment would be done from any single address wallet or specific single address wallet. This works only in chat messages.
To request the user to pay multiple payments at once, create the below Javascript object objPaymentRequest which can contain multiple addresses and multiple assets, encode the object in base64, and send it over to the user:
The user's wallet will parse this message, display the multiple payments in a user-readable form, and offer the user to pay the requested amounts. Your payment-waiting code will be called when the payment is seen on the DAG.
Waiting for payments
If you include a headless wallet
1
var headlessWallet =require('headless-obyte');
Copied!
you can get notified when any of your addresses receives a payment
db.query("SELECT outputs.address, amount, asset FROM outputs \
4
JOIN my_addresses USING (address) \
5
WHERE unit IN(?);",[arrUnits],(rows)=>{
6
if(rows.length ===0)return;
7
rows.forEach((row)=>{
8
// react to each unconfirmed payment
9
});
10
});
11
});
Copied!
arrUnits is an array of units (more accurately, unit hashes) that contained any transaction involving your addresses. The event new_my_transactions is triggered for outgoing transactions too, you should check if the new transaction credits one of the addresses you are expecting payments to.
Waiting for finality of payments
To get notified when any of your transactions become stable (confirmed), subscribe to my_transactions_became_stable event:
db.query("SELECT outputs.address, amount, asset FROM outputs \
4
JOIN my_addresses USING (address) \
5
WHERE unit IN(?);",[arrUnits],(rows)=>{
6
if(rows.length ===0)return;
7
rows.forEach((row)=>{
8
// react to each confirmed payment
9
});
10
});
11
});
Copied!
arrUnits is again the array of units that just became stable and they contained at least one transaction involving your addresses.
The above events work in both full and light nodes. If your node is full, you can alternatively subscribe to event mci_became_stable which is emitted each time a new main chain index (MCI) becomes stable:
1
eventBus.on('mci_became_stable',function(mci){
2
// check if there are any units you are interested in
3
// that had this MCI and react to their becoming stable
4
});
Copied!
Sending payments from chat bot
To send payments, you need to include a headless wallet
1
var headlessWallet =require('headless-obyte');
Copied!
and use this function after the headless wallet becomes ready:
// something went wrong, maybe put this payment on a retry queue
5
return;
6
}
7
// handle successful payment
8
});
9
});
Copied!
asset is the asset you are paying in (null for bytes), amount is payment amount in the smallest units. If the payment was successful, you get its unit in the callback and can save it or watch further events on this unit.