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
- 1e5694c163ccfdcfe4d9b29d345a402df7a8bb89742d3e6dc8bee1ec7d3a3863
- request
- 0155c10b67c59010e1c64d2a0a1950a208bf6e2062d2d03ce45c58d022b99c90
- transaction
- 6df99c28b7d6a501285ba5beac91ffc0d49e19cf6f9600d3f2dfc0964e0d6640computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54490
the chainentry 54490
- sealed to the entry before
- 10bd271aa6406f573c3e38a6fdff3eeb1016fb9768f789cae8f6d1962babff74
- this leaf
- ebeb539a62ee59f61737ad6fa3d3a0509b3bf34e146ac33f16cc5610ad959eb3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V7RbyxqM+Ww0baNlGBkupQJvvow655hdYOTXgfYP578pgTYFH1y+Ne0AAwxUvwmGoGl/vIxl79PWn5AG1MoeCA==