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
- 700b20b4389ae437a2780ed98499f72cbd335d9949e39c01633b5d894b96d18a
- request
- 98bb8c04779cac81b292cbddddc72418fa0e50742b1088e31751e7f8fc9f1551
- transaction
- 7e1690a474705bf155e61b0f84556927cd3751f06b8809a3d3361d7127fdb648computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36288
the chainentry 36288
- sealed to the entry before
- 79f64b723f1baf21a2a268fadee2ef9f211bfb60777f22d3bb95743d9471d063
- this leaf
- c7ce3c040766c9d24455d95d7a13078ed0562786531278a531403c7d203a4c6b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ctfuf2VUXc2K85NBs+QG02dw6069AV4vDfV0y9lEKpHxapHiwEj+85BpS5ERsDdnHAvWmTlRjcKyohAzKVG6Aw==