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
- 004fed4cc481f5c9807d2cb8bdc3d564b9cdf99ebfe42ed2e6fc025d3bce02be
- request
- d24ec17b3c7abce71463ad28ad50dc3c440b25f34c2b2c7c2f36cb740ac01053
- transaction
- 0d985cb524216817d5030415fe3c9e3eab28594b4c4db5e03c8ff7271e84f4e1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38358
the chainentry 38358
- sealed to the entry before
- 64fb0ac565e0829db3eaa8dc258a6b5a4389f7c1fae67258d8a64496fb029456
- this leaf
- 1170ca3c5edb4ff71b77da2768256af54eee7a27a9ce621d3be1a4b55afca979
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PiKPRx7sBFSoxbp1Spu9Dyta6/MHK1jwlOJQ03NgaknEAFvODBvwdV2zbZjIc6rfcHmA9Z+00re+HOyDOPvwAw==