Some information on the details, I’m a newbie on these so please correct if anything wrong.
paymentPointer is the address being paid to, when a transaction happens uphold generates a unique address for the payer (most likely Coil) to send to in order to adds some extra privacy to payments.
When you are validating transaction you should have some knowledge of the paymentPointer that should be used and discard invalid paymentPointers as that is probably something bad actors would spoof, which could mean you are just validating them sending transactions to themselves.
assetScale is the number of places past to the zero needed to get an amount of 1 of the assetCode. This is important for crypto currency as very small amounts can equal large amounts of currencies like USD.
amount is the amount of the assetCode sent relative to the scale.
requestId is the session id for the payment.
assetCode is the three letter currency being paid. It will probably be the crypocurrency XRP but it might be other currencies depending on payer in the future. Even if it is XRP if you use a service like Uphold I think it immediately converts any value sent over the Interledger network to USD (or maybe to whatever your primary currency is) (and on Uphold itself it’s easy to convert USD to XRP if you wanted to for example). https://interledger.org/overview.html
receipt is used to validate the payment. I’m not sure how to use this yet. https://webmonetization.org/docs/explainer/#flow I don’t see for example how to validate with Uphold. https://interledger.org/rfcs/0039-stream-receipts/
The docs say this but I’m not sure how to deal with it. If you care about the total value of something sent to you it should be something you figure out how to deal with.
There may be multiple STREAM connections for a single
requestId. Therefore, areceiptamount may not represent the total amount received for a givenrequestId.