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
- 307ba5b64da13cb03098e3d378778b2d7a770ed30cba600f7012c1a079be406d
- request
- 272bf487550b283cb10bb56a4955b263ddb0fe5a4ba453ab3c490c9a60124ac8
- transaction
- 6ef0fa686c01d028a9a2a67b5cae173f77a5a1a3d02560523dda0e6b8490de6bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16066
the chainentry 16066
- sealed to the entry before
- a1122a2ba81c65c2efa89973aee82d6e00dc40639cdcc458786d04c9fb1c2dfc
- this leaf
- fade93104ce589fe62ea7a84f97cfab8c1c60a111d124103c07e9c26fca2218f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4wutIZWi2asphv5ibdgnJOHx504rRDJfsAebikk5xRQ5Vo1Zpg44KSA0eK1aWrSe0uSXFObqD0ObxA65swBMBQ==