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
- 9eae7826357d990c491dbf199f217cd41a88854dd916e0d9af409bf17377a339
- request
- 5c388460e8409e25d5e91ebe04ea8735eb2bd95897d77a386656c015a815452a
- transaction
- b2e5b6ffb89d43809ed32210b568a2ae8dd0a362a9d5064eb63ae928f0873695computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25220
the chainentry 25220
- sealed to the entry before
- 289e6b897053e1a91e864cc3c542e950fc754ddcb186aa70cefa8e05bdba3bcc
- this leaf
- ff65e57570806fa1642ec45bde5f0fa7e7118f0f28d51d232088935426b9c447
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l0UTz+Xbo3tAQaNaAVk+MMndg3RUvNwpkx5CoUPnpocVMYMB5vmemiHyVwpQ1Eijs7HIwVNKpHeFQbBVnpm9DQ==