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
- d188a2a33da93c9674a60e48a80465ed8b21443c8b35a86df7efdb19a0952d49
- request
- b81545f8e1168eaf1015e16bc94e8c5d11b8dc665cc351cd454adc511d7cc30e
- transaction
- 5389dfbcdedee5d4a600e1cee3d88bd335dc3682a41b1a07ab1ac8a088faa96ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64445
the chainentry 64445
- sealed to the entry before
- 0f25ea4b5a6f8f28ee396aef88d79b62f68ccd4f60f85d5820e6c1941367f64b
- this leaf
- 949714a914c3a2a5c928e5148d3af278ae914af66a20da9f2ffd8be7fce57672
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6Lm2/17IhydZHWOgRAx3/NSjKbJl2kKUjtcXPpeVeEsW9LdFeaJUs1K0IAI8igENNEYnShr0LlbE9McT0PeJAA==