Developer Questions

I'm currently trying to sign a transaction by providing this payload: { "txjson": { "Flags": 0, "TransactionType": "SignerListSet", "Account": "rh5QhvyqTg2QTZdciXkDdEnDmJfuQvmuF7", "Fee": "12", "SignerQuorum": 5, "SignerEntries": [ { "SignerEntry": { "Account": "rPT1Sjq2YGrBMTttX4GZHjKu9dyfzbpAYe", "SignerWeight": 2 } }, { "SignerEntry": { "Account": "rPd9oB2Kdot9HSsXSeFYpKZUV3vDsBzv73", "SignerWeight": 1 } }, { "SignerEntry": { "Account": "rhx2Ru7kb33w8UP2iRCCpVYPdUGyKAdhMZ", "SignerWeight": 2 } } ] } } I'm receiving this error in Logs: Internal error code 1217 Error (detail) message No permission to create this type of sign request. Contact Xumm Support (in-app). I'm able to sign this transaction locally using this exact object without the "txjson". So the problem can't be from the object format. Is there limitations to what type of transactions or fields we can pass as a payload? Thank you, Rambod Rad

Hi, How do i create a web app that interacts with a XRP Wallet? I have been assigned a brief to build a simple one page web app that when a user clicks a button "connect wallet", the page then shows their public key and address? Their private key and other sensitive information is only handled in the backend. These keys cannot be exposed. Can anyone suggest where to start? or perhaps there's a tutorial online somewhere I can follow? Thanks

[https://xumm.app/api/v1/platform/payload/{payload_uuid}](https://xumm.app/api/v1/platform/payload/dacdfb2f-01d5-4b6c-b30c-d822f6340c4c) When I sent payload api request, dispatched_result returned empty string at first time. And after send api request again, it's returning 'tesSuccess'. What's the problem? How can I track when signing transaction verified? Hope your answer ASAP. Thanks.

Hi. I'm trying to implement OAuth2 flow in my project and verify jwt on my API. In documentation said that JWT is signed using HS256 <https://docs.xumm.dev/environments/xapps-dapps/your-own-backend-auth> but when I debug jwt using jwt.io it says that algorithm is RS256 { "alg": "RS256", "typ": "JWT" } Is it intentionally or it is a bug? How can I verify this JWT on my backend? Because documentation says that I can verify it using XUMM Api Secret but RS256 is actually asymmetric algorithm. Thanks

Our platform is an e commerce platform, think ebay / facebook business's type of app. We currently integrating xumm/xrpl as a payments solution and are interested about finding out more about pathing and using gatehub as an off ramp. With respect to pathing the store owner can decided what he wants payment in and the user can pay in what they choose and it gets converted - is this possible via the xmm sdk In terms of off ramp, what is the best possible solution ? If memory serves me correct im sure i viewed a tweet where by you guys mentioned you can use gatehub - i have searched my bookmarks but cannot find the reference.

I am using the server side SDK and i am successfully creating a sign in request and logging in via the always link returned ie <https://xumm.app/sign/22fbdc2a-2e36-43ab-b609-2f65edaed49c> My sign in function looks like the following ... export const xummSignIn = async () => { const payload = { TransactionType: 'SignIn', options: { user_token: true, }, } as any try { const subscription = await xummClient.payload.createAndSubscribe( payload, (event) => { console.log('New payload event:', event) if (Object.keys(event.data).indexOf('signed') > -1) { return event.data } } ) ``` console.log('SUBSCRIPTION ', subscription.created) return { qr_png: subscription.created.refs.qr_png, uuid: subscription.created.uuid, always: subscription.created.next.always, } ``` } catch (error) { console.error('Error fetching XUMM payment URL:', error) throw new Error('Failed to fetch XUMM payment URL') } } The response object comes back in the subscribe function but the issued_user_token is always null ie issued_user_token: null Any ideas ?

I was minting NFTs from my Shopify app and signing with Xumm without problems until yesterday. Could you please help me? Here the info of the transaction: - Signed tx hash: 9261114965EE879FA842814EC1FC880FE33E6CA9F5C7F29621243A4A4E72C906 - Payload: { TransactionType: "NFTokenMint", NFTokenTaxon: 1, Account: "rDnHqD11jB9HdFx3YmHTbQc8GScDd8BQfM", URI: "697066733A2F2F516D53696A6139567774687459417070627762346E3769476F3647774C534B79735742647A655673344A4A6A6F33", Flags: 1, TransferFee: 10 }

here is an example of how im using xrpl to batchminting nfts, 100+ nfts at once. how can i do the same with xumm without having the user to sign the tx 100 times. <https://xrpl.org/batch-minting.html> ```javascript const mintBatch = async (account,tickets) => { try { const mintedTxs = []; for (let i = 0; i < tickets.length; i++) { const transactionBlob = { TransactionType: "NFTokenMint", Account: account.classicAddress, URI: xrpl.convertStringToHex("some url" + i), Flags: parseInt("9"), TransferFee: 100, Sequence: 0, TicketSequence: tickets[i], LastLedgerSequence: null, NFTokenTaxon: 0, }; mintedTxs.push(client.submit(transactionBlob, { wallet: account })); } Promise.all(mintedTxs) .then(async (txs) => { console.log(txs); return "done!"; }) .catch((err) => { console.log(err); }); ```

Hey Xumm team, What's the process for submitting our app? Are there beta-testing steps we can take, for example deploying the app publicly, but have it only show up when people scan our QR code? What we'd ideally like to do is test in private beta on the testate for a while, where we invite people to test, and anyone with the QR code or link can join, but it's not publicly listed. Then when we're ready to list it publicly, we'll switch to main net and publicly list it in Xumm. So far we've been internal testing with device IDs, but we're thinking of testing with a few hundred people, and obviously that's not well suited for that. Thanks! Julian

Can the escrow(escrow creator) be customize to connect to a database with multiple wallet address and distribute a certain amount of xrp from another field in that same database?