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
- 7ce2050e5bae4b5692dded5cca2c0f30933c4c32c03cc8bfcd712a18154d1f0a
- request
- 2a2c08a9eef8f70351b4c57d428928962e8d3bc64bd7fb1d0574b50b5c0ff16f
- transaction
- 2136f3bc846cf98d4628f7f137c6bcb54e96394b22d12da3bacbe0bcd412a405computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37546
the chainentry 37546
- sealed to the entry before
- b6f49b48e916b01bc684eb55d44d0d0b40485bd72fef1f74d024ebc527dc229c
- this leaf
- 382dafcfdaca323ce1f7a543598da1b4ea8eaba12261dae79582c221da0057cf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0INHTFsDP1oVaouKfQGC5+/+VIsVokmAJByQ5xrwBABYk0qGXKc7aMPyoqP1y7SKTbI2omWZBASfDLbJGvDGBg==