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
- 22d511144e21c8d166cfa379eb5c2256bd154a00167639cbf0147b7468393245
- request
- 8e053436f0d760ccaf7f63ffb8c452ad9e88d4239322fc463d498bed4b098fc6
- transaction
- aadba5e8f28455d9aeffd148cf26c2f4939c3b3189a860301e2dca9b8528e769computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72888
the chainentry 72888
- sealed to the entry before
- 2e8f0df340da3b63e52f7cb6d735f06afedfd30a08e07f657ffe1f4b7f793e7a
- this leaf
- f9a96c1c5c43b5a8e600e678ae2ec5d970a4d0f19dfcb758e0692907c33516b9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Dr+TKihBwLlNzxGw5XHuc7rYzWembVqDF4apkM9MVr6e8vOdfl6uvWEHtAFQ5Qp94P0d+NVsProHEJi/H11wAw==