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
- 91d97c79129d39f34095ef2ae38200dd7957e97a0d9b6499a2454fab29912abf
- request
- f75623d5c7021e2cf0ecc28edc2171aea5da6edd6d34d8cc2dbee2b1446b421f
- transaction
- 7c096a8265dc4dd8f71636cde8a0907669d47d54cc7a4b5bf6f8db9086ec52b6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2105
the chainentry 2105
- sealed to the entry before
- 5091ce2c8660ab69e8e0e3e4928d6dd6012ee9be06434bff2753a4a5cd55dc3a
- this leaf
- 49fc75c091250a2bf1d8d346da0954930a287e37d3d7520a933d3ec10f98688c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DO4UZKbXsobUiQ75Slt/mAvj5x3kTM2DhnrEadEM6wNJHae6oMtsucnocK0LbFWRf7mTpsGQHXpdcCSy1ByBAg==