The XUMM API will allow developers to deliver sign requests (payloads) to app users. A payload is a JSON formatted transaction template for a transaction on the XRP ledger.
XUMM app users can scan a QR code or receive a push notification to open the sign request for a transaction. A user views the sign request and either authorizes XUMM to sign it or rejects it. If authorized, the sign request will be signed locally via XUMM, if rejected the sign request is destroyed and the transaction does not happen.
If authorized the transaction can then be sent directly to the XRP ledger. The initiating application will get realtime status updates and after signing, the end user will be returned to the initiating platform.
Before beginning this XUMM SDK tutorial, we assume that you are ready to code with your code environment already set up and if required, you have followed the steps outlined in my previous tutorial.
This tutorial consists of five chapters:
If you want to learn more about the XUMM SDK, platform, documentation, etc., make sure to check out:
- The XUMM SDK readme
- The XUMM SDK source code
- The XUMM API documentation & API reference
- XUMM (end user) support docs
- In case of questions: firstname.lastname@example.org
... For checking, correcting & testing the SDK & tutorial!
@technotip, @calvincs, @wenusch, @alloyxrp, @rippleitinnz, @Ubbah, @enclavia, @WormholeMech, @Chicles_, @3N0RYM, @XrpSpark, @devnullinator, @Vetjes, @KevinKing64, @Kujistudios, @nodehash, @4thMadHatter, @Vkumzy, @CarpeDiemXRP, @Hex539, @xrplosion1, @chemical_realm, @RossMacFirdeen