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
- 06a413a3e7e2d71887d3793bf0d52aada1eac255dd82541580a67db87d74ae62
- request
- 39a9ac11db419678cff6d4d613162f0b2215e338164a3df4232db62645c232ed
- transaction
- 7815a2effe5e419ad2ab5761b10105ced4021d9bd93069ad25c8af8ba61caae6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34660
the chainentry 34660
- sealed to the entry before
- 876216d72c2fefc007c41e6a5d07221160f9a246e9de6fa0f2448fb927e8a0e0
- this leaf
- b5b285935d33a2e8c93db1c5aeeb317d63179bce2a950d651d84ceb46346ae11
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- alexWk9Mn5+9nylbz5kMXEku3/pbjbRB09WwMUXT+o057WO4fgJjlxIoBtOEd5zEctmZ37xw1nw0kWoL32z7DQ==