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
- 605c470dc1fa5ef8c55bdccfaa8f287fe406a8f8ce865b80c341ef0e86690384
- request
- 6cc7dc62242d20d2e367c0d218a9e191d0cecd3eee82132410862da0338e9858
- transaction
- 296d661ee94b5df2887019fb98ca5e8b36e1e170436910e98b5a14864b56b810computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63735
the chainentry 63735
- sealed to the entry before
- f3e2c6ddbf79edc62e8c9edde34400c4e721d27bda5fce4492ebe8c7e103e488
- this leaf
- 92d168364af7cb5eade84d4b8c5c0473f3fc6adeaf71bccdf1bdee228f88bb87
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AzAPhw4xaWKed2Icn/sFlVdLvDIFYRFfTcY3lMucQjIHMpb+M/SD8yzKkKRexfWY/nyhouZW6azi7LhQxklSCA==