Skip to content
Client FPS

Save FPS Configs

Saves a set of customer FPS (Faster Payment System) hit-rule configurations.

Request parameters

  • Required: fps_config_records (list of FPS rule configurations)
  • Optional: audit_frontend_resource (caller audit context)
  • See the field definitions for each field's format, allowed values, and business meaning.

Business notes

Saves customer FPS hit-configuration entries in bulk, defining how the related risk-control rules are handled when hit.

Result

On success the submitted FPS configurations are saved; subsequent state and returned data follow the 200 response definition.

POSThttps://b-api.lbkrs.com/risk/v1/fps_config_records

Authorization

AuthorizationstringheaderRequired

Send the Broker ACCESS_TOKEN as Authorization: Bearer <token>.

Permission

lb_hk_credit_limit.client_fps_manage

The Broker ACCESS_TOKEN must be granted the permission above, or the call will be rejected.

Request body application/json

fps_config_recordsarray<string>required

FPS Config Records. Array of FPS rule configurations. Each item contains:

  • config_field - Configuration dimension, such as client type or risk level. Use a dimension returned by the FPS configuration query.
  • option_value - Value for that dimension; it must belong to the value set available for the selected config_field.
  • fps_change - FPS score adjustment submitted as a numeric string; positive, negative, and decimal values are supported.
audit_frontend_resourceobject

Audit Context. Contains value (an array converting config_field/option_value into Chinese display labels), $behavior (fixed text "Edit client FPS rule configuration"), and $action (always edit), used for backend audit logging.

Responses

HTTP 200The request was processed successfully. The response data does not contain additional business fields.
Standard response envelopecodemessagedata
dataobjectdata structure

On success data is an empty object.

No nested fields

HTTP 400Bad request. Check the business error code in code and the error details in message.
Standard response envelopecodemessagedata
dataobjectdata structure

No nested fields

HTTP 401The user is not authenticated, or the login session has expired.
Standard response envelopecodemessagedata
dataobjectdata structure

No nested fields

HTTP 403The current account is not authorized to use this feature. Grant the required permission to the account in User Permission.
Standard response envelopecodemessagedata
dataobjectdata structure

No nested fields

HTTP 408The request timed out. Check the business error code in code and the error details in message.
Standard response envelopecodemessagedata
dataobjectdata structure

No nested fields

Whale Docs