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
- bd83c10cc5a47954c6a7bd521cdf8491a9cade00bcbd9bbaf41495d53566ec29
- request
- b4e784b5312301f5ccb0646aa759f3c46ad85d32aed8b19689dc7b67354fafb6
- transaction
- 1091f927e807abdd8d63f2d500d7e6422db103030bf9a05f61a57e9571b18931computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51497
the chainentry 51497
- sealed to the entry before
- 8dfaa831db9f8ee19ea8c552dd629910d079da3f97d77b7eb36afb1eb67001a5
- this leaf
- 0d2fe3cd13b368500dda40b9c31cd9fb273ac6cf018dd3b7830e1a7c7832a914
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PkEK/uWtcvwhEEeT0/7t6asSGNioUoxIQXBGhIOWyRloAP/CrRYg1lJxQngLvg7ytQ7sCVH9AEJXiUknyYlEAA==