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
- 2f4e7c1af015e86645d44d3a422ba62da85a54c46f61ac240026adcc811fc47e
- request
- 3828b5b14e618cafb39e22755089d45db819f6929423a94e94cffeffa7e3b907
- transaction
- a0f7ee75ba28aa0e9bd00342e6ecefe8a1e38681ebdecb9f87575224f39c43bacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11888
the chainentry 11888
- sealed to the entry before
- 0e533aa342e71af2d085103ed852744daa8788c2ebb66e82d7e1f5fa63e156e0
- this leaf
- 137b1d44c99c588ffe1b55c67846e75323a12faf2516578a190d77cc053291ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d0aeZk7MlA2gCMDEwljxpeAAFJcAKDD56AuqhDIev9NIKFPBTisfNl8PwiySwtWKgVsI7B0Dtw+kdL3TDVfhAg==