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
- 934f668d23867fda3dd212256c17ded51d75527cc36c669529205ebfee8dfd58
- request
- 7d02ebac3cb12028d6bafb1db5bebade7b6acd218f1dc6a746b6c10fad28d332
- transaction
- 684b5189012c41400aef645fddeb1d173e6e31bab5f1713ed30a0664174bf934computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30268
the chainentry 30268
- sealed to the entry before
- 04b098e656d0f7e56fc24c404825bea60084632b4477ec50ce430cd3afcf184a
- this leaf
- 8175048d9b10ab6cf0cc7ade8b0f69ce47627f4ea5b1878e0f6e324cc4d3e984
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JzzaIHmZj7vLEOiHCYQeevhAD5Xd8IZGPrtobjHu9SE5XD45noVdpzJ6FqyzLuXa1uvym9v73DJS7VIPEQ+7CQ==