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
- 823408ad7f40f3927907387e87422db25740ad3aa478fcd0202ad65a7af5ef77
- request
- 701493c732fcef6896fe177693a32dd2c13003ca1bac830b53a0f320d1cc4241
- transaction
- 90b16e23b7fb0239c0518cf6e3935dea3303186cfdf4af897c51a19d871e8ed2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30156
the chainentry 30156
- sealed to the entry before
- d854fcdf45845e26a0515e151a98d75350701d2a494089518c5dcb14dddd5ca6
- this leaf
- 7cfc1e3db8ff9712bd54d2f900af8d950d08918f5b94af44dafd49946cc58dab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jaBiW9T+iWlxysboZ6ga1t3EMs0WeLt+sETwEaiP9AbwzjpdEMsZdC1+rR5Ion5oX6dAiCsnjivweLXH1W8pCA==