why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- d2860b142381b53b8dbe16671fdb99f940bc8d809d009d6bf84e2dca7a370473
- request
- a2c421498ed5b67da85e457663c60177033f332444bd1a04611df18fa4b4a2d1
- transaction
- c82698769c23bca32f27578c30ee935723945d3d388deababaa261b8942a4cf1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11549
the chainentry 11549
- sealed to the entry before
- c68fcac3b2227148a6666c9a7f9458ffc804005dd8bb404634af9b7e01de07e9
- this leaf
- 7a14eab96532fd6857cecd6f6e12a1c77fa1a91acbf573b4e56c85b1e81b84c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LBLgDoIhhVg/A2Bx3bqB4Z0pYJ1BKcGhLT+CG9M8RRGZxjEPl97vgjhBoibawCwPTz5U2Hp8ItaB0GAJVTuFAw==