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
- e5c95984175dbba75545942d07a671958b89c359a5d21d22ab745e392cdca56e
- request
- 0c027f68a2c7580e49458effeb47608d4fda90a0dbfbdf41b7beeb994a1fdfb4
- transaction
- 25c13c2f6218425c9e487d93fa603f25928a80c52431bbb95fb918a0bdd5a5b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17320
the chainentry 17320
- sealed to the entry before
- ec362153a61f72975fe066a72755a14885b9fee992725ff04891e6b15d031946
- this leaf
- 0023c944de6d267fd282a2cae6ec79c83b11aea6022c8367e82dd4edc3daa56f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FB0kZqcbY571G2K7/OkzKL7BDUtcgu41kpckEtzg1oW5GajSz0nK2wIIYELaBGUs2FPGoGhkXGoPXjwmoWjrDg==