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
- 3d8364732743d37dea9ec48c76eaa4397f7948bd21685b8af30cb3d2259a705e
- request
- 82d482a1054f3fdb674317367b2a3b4c5b98fc65327e6bd4a66630d6d009ca1d
- transaction
- 4269113ddb3e054220e25b9c0b26423e9c4db29570c65a81369909aab811510dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58026
the chainentry 58026
- sealed to the entry before
- 67b5e3f9624c02d1320195470ae37678bc6f0091f48e54ba7987074e824d3c5e
- this leaf
- 8a7cfe0b64e65ee3976b12187c958b0516df7ad0b99a5f119a29bbac81ab80de
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OTZxYc10LxROe11KiEFr+Yyy5+k6zNbikHx1Oq0rFNaCu64bH7oBTOEKxzUl7idpKG+LOK26+2Zkw/2VWRe3DQ==