&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).objPaymentRequest
which can contain multiple addresses and multiple assets, encode the object in base64, and send it over to the user: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.my_transactions_became_stable
event:arrUnits
is again the array of units that just became stable and they contained at least one transaction involving your addresses.mci_became_stable
which is emitted each time a new main chain index (MCI) becomes stable: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.exports
of https://github.com/byteball/headless-obyte/blob/master/start.js.