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
- e590ed78b5b635da599973a58dc75de1494eecc4abb26c91bf7088de8d653517
- request
- 475eb2ad586d3006eba3e9d72fbfb581405b2205baf6a1232b00af9d101a7689
- transaction
- f7a3371edb8d206d0aafabcf9c0bbd0830013cf5872fd01b507e0db5bf9f5823computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48321
the chainentry 48321
- sealed to the entry before
- c9b1975336f3f55022ab98021573567ba82e7ae28f7c69a1d21a09300fe37476
- this leaf
- f0f43ecf871988c4973f01b8314b45ac2a095276daadeb24381642ab28690952
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +AzXxCfUhtEu9xGVd5Cpuz3C54/NgZcppsFVevPx/S0u6nlwYTgD+mdZqo5p/2HP7n0TNBR/5j4TK3JX7M68AA==