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
- e718a3ba4d98f95cb344b1601a4fd4fde593e55a26b36710fda0379b425ad58d
- request
- 27b83e49406cabb6c8dde4ef78d0e79bd57f36b51f614fe3b29c3d89cabf2932
- transaction
- 2c4ddeba7a13879ba7c374d3d4e44c68f18c2fbca2e34f09f7ff6a9ed428bc88computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56186
the chainentry 56186
- sealed to the entry before
- 29105f7dd22f304909a7270a3e1a82604d4c661c8053c35c3a4e7d3dddca0eae
- this leaf
- 9590fc2bcc77e9c2f239da29c81db84ff969493510d66d887ddb3730f5300a3e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PBoFXSTCnWAOPHC40hk837JxpP68jlHDoa2H9+O/i5rpytQGdOaJJe5e8PA4YBrc99mQ07N/Zm56fQV+s2F4BQ==