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
- f4dd81cbe5a27ac00c00f9c60efff2793e8b44f1b0c31a7c345f41247c400845
- request
- fd35fb7224fd16fb2c0af0fb36d7a1fa1029bf2b75ac040881524dcfd2f77bba
- transaction
- 09de1d7668250bda2d502815bc5a2c43e5cc110443f5374678159e60eabb5e40computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41
the chainentry 41
- sealed to the entry before
- 78c4e4156375b542891ddf857a7744d032b3419fa1c9572097ddac954191f4d1
- this leaf
- 9c74a4170e18790339310277cf57353f8898d61c97cb11acb153e1de8ea03061
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +LGe2FZhfb9aQ3Iq4s0GRXgP6gLweOEyyX4JpNIfjJ/f/sKh0yiMOV6NGgAXOHKbIk024P5WcStRiyFrCiyUCA==