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
- f8672e7d8a3f59cec9f20d8d26939000b3f5ad9d98e72285ba8a444ea4e5a73b
- request
- faa1095303e60de2b25714205b504fd92d297949d875f7b6b38b85489c5bfd0e
- transaction
- 747c4ae68ffa172bfc9f20b43700dd9e03efd1ad3933150dc340a8476f11f3a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 761
the chainentry 761
- sealed to the entry before
- b9ba631bac71ceb047cf35cea92904f3f8c6026cdcf897838a3e62cb52459d2c
- this leaf
- d78621755c21f3bf92a27d6eb42e5f98b8683d86758e1b629bee780d91bae96a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CMADyloXfXHbREbR/CkCjC6vK4VszRwAGBUtm8CyT+f66LTVHIOVL6yzpM85zfnY+6VbGqxqhmwsULdwv74zCg==