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
- 6184bdc4801d217509e1fd82576c68a1d98b984683580bc70d043d90d55b415d
- request
- 47acd2031598b481f42287137d746701a82cd6fcffb220b054e9d4c50b0cdf2b
- transaction
- a76dc38c4e0d65072c5e9bdd043c1769fd815cb30fec902c565902653969e247computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27819
the chainentry 27819
- sealed to the entry before
- 652dbe09830f8bee5aa93cf993cbda26de7e36e9540fe6edbc74c2071ca80dfc
- this leaf
- 47028a0b14b9e854534f0571d2e250f2afd4e598aacdeb9a3aff4a852a9992ec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FlJnYme7DBInV6HZiETYBwpc2PrG57H4IM0i8Z4JjWrBEq95Hrdc6srF06r/bzqu2AZOlywDU+uJlwFA9voQAQ==