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
- ed8923a0a9a32f37c7fd28d9bbfb902713a28c1f15739ee33e36501b88a859c3
- request
- 411689c084f9b78093b02b6c476352f08dc56879ecf4b33ec718601c21af46bc
- transaction
- f654181d0dff942136a1b8604f82b5d4f5486dc330b83280270e7c70bcb36380computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47566
the chainentry 47566
- sealed to the entry before
- 1b589244b5e085146bb15c8eedb9aa40d3dc2bff268baf7904da24ee7e633cc7
- this leaf
- 0317291bdaab66d3e12e7ac2a4baf0cba5a3c17bede7413fb3b78302807dcd3c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9WdqF229kgKcsKhjUVQjNSBCxnAERTCYdnjAKUs0TSBkci3EZXppgHCkyTmHYp/4WvDwQOQDdinGbHfZPU7KDw==