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
- f0db0473985c69633a586d02f89f112ce647864240e8aff05f3aac23394918dc
- request
- 61aac1fff576c47c855c2f028eced82abb07559420a595fc198c68ac3b5a1f74
- transaction
- c4fff05c7c4e70944373d41b9fb53009d8f76be0e4b366c93a06e333d04e83e8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47055
the chainentry 47055
- sealed to the entry before
- 830a61f7ecc6ab7442541dd9a7c8d303014b8a999c1a7518793235d02bef2ff7
- this leaf
- 7bc6d1e7bced82bd4339be156af2156319b7da604c514288fc6d4ed3e945bb89
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Iaba9tcuwK9TsUwZ7KPE8qTyuacsxWUyFyJnePMspHhXc7XBvVpb/5NGJwhCkP2C82/gbof8JZ+qWeNuAB2sDA==