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
- ec8fe750f5845f6561312fdff17a1e3aff2f7206783b96978f11ef9a5787d89c
- request
- 42164d178c0459937e47560627d9eca89bc63822a636ec59732fbfbaeb4e16f1
- transaction
- 770154a07381d31c11ecfaf85101cc4d7fab5e839df3311a279c36799c3a5754computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22283
the chainentry 22283
- sealed to the entry before
- 099d5c6c6a97c83cb94d79eba9628abe9d122cefdac66c3d1a678a0c681a1667
- this leaf
- 55e0c07c90c1410836d334cf2c40b9adcd2b9f73133279ecd9923395dbde84f3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L3WVaTT19bEYmkyYEH260HPpIM1Xlt3UkEGgeR2Q7HtgBKSEJDj8uocFZoayiheCIutuViX5d4EtwvdtNRb0CQ==