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
- 40a4d0eff242b6fa557ad40f5df54bb163aba9e0d20afe838af4532c97759691
- request
- 52cd2bfd2284812e7f179c53813cdd763cb4e5c9a0d6e32580f3f11dec9b93d7
- transaction
- b653256ef73d47ea854df31069ade4c8fae1add6ba2ecc90bd6dae69623e9c43computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9847
the chainentry 9847
- sealed to the entry before
- 1607f0248876f3ff3a00995e4c273e32934bec8d31d9eeaefbcac5dcb9a8d7d0
- this leaf
- 821755836b4f912f733286d1d1b89dbd17bdb064972bb3b6a8535994021edd91
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UxV9VwM1BNlyPCVmZAniFbGsYgDU9urJOyeDtXLBUa7s0nX+OfzLeSa0NX16FWiSGDTyJsXrCj3bolBBZQqzDw==