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
- 9c430390dc25a10bafa4a681b109e0214d5bb50917d5541bd0ea30112480ece1
- request
- fef6d8e34f0e3ad297affd60e44430a3f5170e92130e69cee033ae9e3585c867
- transaction
- 4ccb4b7670f0d95ebb5081fae2d77690296224251464af83aebb77521f9019e0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42059
the chainentry 42059
- sealed to the entry before
- 051ef0a0d3380f57e56bad00728cf46c63636478085b116f7881c84196c88f7b
- this leaf
- fa271d765e25779890b53ec3e0247221729ea804253ca5027f7604063adc592c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bK2hBQdEC90hzQGKoYePyBKrxC9js6uN57e4p/7stlKRkfM+bosJap7NPIMXMCuoPf3kSQM42EMCke6R99u0AQ==