Delete the screening policy for a vendor
Removes the environment’s policy for this provider. Screening reverts to the sanctions floor alone, which is what an environment with no policy has always done.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
ID of the environment
36^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$"95b11417-f18f-457f-8804-68e361f9164f"
Screening provider the policy belongs to
Screening provider a policy belongs to. Deliberately not ProviderEnum, which
is a 44-value auth/social/onramp list of which only these two are screening
providers. The Dynamic sanctions provider is absent because the sanctions floor
is generated from code and is not configurable.
trmWalletScreening, chainalysisAddressScreening Whether this is the sign-in policy or the transaction policy. An environment holds one policy per provider per scope, authored independently. Whether a policy is the sign-in policy or the transaction policy. An environment holds one policy per provider per scope, authored independently — a customer may alert at sign-in and block on transactions, or skip the paid provider call at one and not the other. Two values, not three: an "applies to both" policy would make the overlap with a single-scope row unrepresentable as a unique constraint.
SIGN_IN, TRANSACTION Response
The screening policy was deleted