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
- 04fd9cb2eea2c4d6e599f74824aca0bb3c1831b6694ebc028b1f97dd5cd92793
- request
- 8cff51adaba96e20abab797b54beaf1eb187dd41a793c1179edad185c94dd3ad
- transaction
- da28057435181974e95882b4a58ed2a14b94d6161d39c67dc8dcb9df7b740a6ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61768
the chainentry 61768
- sealed to the entry before
- 9841124cb9af67b0846d873185d192c228e6df38c7c74b7d7e352d4411c36568
- this leaf
- 22d5f86563e0962b27a025a5b3a5d5a22e7bf975dbe54ed585a573527cc86ce8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Xz2wNK5HmGFviAWiJQBwKvEUzb5n1tFxGPIpxheKDeSAPbOdlWc+IxCVY4itJEX42ZMJLrbJfL5ICNEIYx/DCg==