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
- 8c734b3d8b27603a5918b6e7977246feb16f9cd0ad60cc18c5ecf6d03f0bf135
- request
- 217503a9d37a56dc08eedda3079bebc6610d7615607843403314961c5b4baeb3
- transaction
- 32bfbe3f356bbd34992d5f8522a0d93e749359bf40cc71e784dbb854a640945acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19737
the chainentry 19737
- sealed to the entry before
- a734787baf88fe9e9a3280f3e545f4e75ea02b5ba2e176fd8e90c37a982958d3
- this leaf
- aa1dcd75f9d875cbf267f96fb57a476b563d69beecf5212826a9b192aaf64afb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VrM5tu6ebFSPRRGhPwh8ACVZ1bgQ3OXUcnJikglDa5gPJ5Ht8Nc1MUkC+3AinaBAgp+Z4iZUdH7ZhxRjLnrrCQ==