Revise payment tutorials, add/remove screenshots

[DennisDawson]

refactored code, new CSS, only one active account at a time, but radio button allows switching between two accounts in the active fields.

[oeggert]

PR looks pretty good, but there are a couple points I have that apply across all functions.

[oeggert]

Can we also add a button to fund an existing account with additional XRP?

[DennisDawson]

I don't know of an easy way to do that using the faucet. If I want to add XRP to an account, I can just create another account and send some XRP. Accounts that run out of XRP should try sending smaller amounts when testing.

[oeggert]

Suggested change

	let results = `\nConnected to ${net}.`
	let results += `===Getting Account===\nConnected to ${net}.`

This suggestion applies to all instances that add to the result field. I think it's worth keeping a log of all actions that take place, so ensuring all results are += and not overridden with =. It'd also like to see a more pronounced headers to identify the type of function that's being called to help differentiate info in the logs. So for an offer create transaction, it starts with something like ===Creating Offer=== and then has a line break for subsequent metadata.

[DennisDawson]

I made these changes.

[maria-robobug]

Question about how we reference code snippets, should we not use this format now?

{% code-snippet file="/_code-samples/modular-tutorials/send-checks.js" language="js" from="async function sendCheck() {" before="let check_amount = amountField.value" /%}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	fs@​0.0.1-security
	@​esbuild/​darwin-arm64@​0.25.4
	assert@​2.1.0
	five-bells-condition@​5.0.1
	big-integer@​1.6.52
	buffer@​6.0.3
	lottie-react@​2.4.1 ⏵ 2.4.0	+1
	decimal.js@​10.5.0
	morgan@​1.10.0
	@​codemirror/​view@​6.36.5 ⏵ 6.33.0			-5	+2
	@​types/​node@​17.0.45 ⏵ 22.5.5	+1		+1
	minimist@​1.2.8
	@​docsearch/​react@​3.9.0 ⏵ 3.8.0
	secp256k1@​5.0.1
	commander@​13.1.0
	winston@​3.17.0
	express@​5.1.0
	@​noble/​curves@​1.8.2 ⏵ 1.4.2
	@​uiw/​react-codemirror@​4.23.10 ⏵ 4.23.0				+2
	inquirer@​12.6.1

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Block		fs@0.0.1-security is Known malware. Note: Package has been removed from the npm registry due to security concerns. This is a placeholder package published by the npm security team to prevent malicious usage of the package name. The original package likely contained harmful code. From: _code-samples/tx-serialization/js/package.json → npm/fs@0.0.1-security ℹ Read more on: This package | This alert | What is known malware? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: It is strongly recommended that malware is removed from your codebase. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/fs@0.0.1-security. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[oeggert]

Changes look good to me.