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
- 8e1ef72513166ef3c86e2f31741ddb0c1d92cf37b42f3c147c6faaa86754aaa5
- request
- 95d37a59c1522dc6365688afd5667afbb807581e581b17360403631de156ae83
- transaction
- 3f63045a5926c203f14556c09b24d6e8e22078ea70556d8c51eae2432658d44acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66654
the chainentry 66654
- sealed to the entry before
- 4ac30739470ad077abd88f5c6381965936f75821756f49e93ee57a62f9c77e01
- this leaf
- 110fc5c5f04f64221d0e935030afacd5da1fb115eb1f8e9d71fdd51db92d664b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0ruZS+dR3q9iKVV2QovAk4RjMZWKIIlRjomPw/CwJrRh3zhVTkQeGxajSM2rkzqpbIzGJiQl+jlBaidutU7jCA==