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
- 8b39faca245e6d2df0536bd844069d9aa47cf7d2fd24d56a5732ab53eca4eabc
- request
- b37a7e91238722919d5f8af17f846b2b06caea18d81ffe42a7894d010eda3449
- transaction
- 995c53403a7c8411878b9227ce39fea7c72a1ef9f169de1a7772705875cd9231computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49573
the chainentry 49573
- sealed to the entry before
- 3b7bf0eff83a8a7c4be411f7c9f084ecae4e40ad027779caf019bab4055e7841
- this leaf
- f87993e81bcf870d21323eebf28b37c99ecac62094fadbb63de9da0265c3d8cc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BH0y7QJ99pKJiwDWXOmq+ZQEAdYMf/AsXnqnImKWQJQHWR2oUhieYhC3CWdlaWMGRLkSlluNt6/Z+eZoWjWXDw==