> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # Create an arrangement > Registers a card/scheme arrangement for a participant. Field presence/type is validated against the schema (422); a duplicate (participant, code, role) returns 409; an unknown participant 404; an invalid role/code 422. RBAC: arrangements:write. ## OpenAPI ````yaml /en/openapi/v3-current/slc.yaml post /v1/participants/{id}/arrangements openapi: 3.1.0 info: description: >- API for Lerian SLC — the participant-side rail that connects the institution to Núclea's SLC card settlement. title: Lerian SLC API version: 1.0.0 servers: - url: https://slc.sandbox.lerian.net security: - BearerAuth: [] tags: - description: >- Settlement operation lifecycle — create, list, query, and control the NUliquid-tracked card operations (NUliquid = the 21-position id Núclea assigns each accepted operation) through the state machine. name: Operations - description: >- Participant catalog — the acquirers, sub-acquirers, IF Domicílio (bank where the merchant receives its sales), and settlement FIs (financial institutions) that take part in card settlement. name: Participants - description: >- Card arrangements (bandeira/scheme configurations, e.g. Visa/Master/Elo) attached to a participant. name: Arrangements - description: >- Regulated transport orchestration to Núclea's SLC — dispatch, recovery, retransmission, and connectivity testing over managed file-transfer, message-broker, and REST. name: Connectivity - description: >- Multilateral netting clearing positions — the net amount each participant settles per STR cycle (STR = Banco Central reserves-transfer system). name: Clearing - description: >- SaaS BYOK (Bring Your Own Key) signing-key provisioning — import parameters and register the client's ICP-Brasil server-type certificate material used to sign ASLC files (RSA, at least 2048 bits, and valid at the moment of import — all three are enforced); the SLC never receives the private key in cleartext. name: SigningKey - description: >- ASLC file intake and status — passthrough submission and processing status of the official Núclea card-settlement XML files (ASLC = Arquivo do Sistema de Liquidação de Cartões). name: Files - description: >- Read-only introspection of the embedded Núclea ASLC/RSFN (National Financial System Network) XSD schemas used to validate outbound and inbound messages. name: XSD Schemas - description: Read-only regulatory, compliance, and operational settlement reports. name: Reports - description: >- Outbound business-event webhook subscriptions and delivery management for consumers (client ledgers — optional). name: Webhooks - description: >- Administrative operations — hot-reloadable runtime configuration, dead-letter-queue inspection/replay, and outbox redispatch. name: Admin paths: /v1/participants/{id}/arrangements: post: tags: - Arrangements summary: Create an arrangement description: >- Registers a card/scheme arrangement for a participant. Field presence/type is validated against the schema (422); a duplicate (participant, code, role) returns 409; an unknown participant 404; an invalid role/code 422. RBAC: arrangements:write. operationId: createArrangement parameters: - description: Owning participant id (UUID). in: path name: id required: true schema: description: Owning participant id (UUID). examples: - 0190b5a0-0000-7000-8000-0000000000aa type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/CreateArrangementRequest' required: true responses: '201': content: application/json: schema: $ref: '#/components/schemas/ArrangementResponse' description: Created '422': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Unprocessable Entity '500': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Internal Server Error '501': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: >- Not Implemented: this capability is not part of this deployment. Operations are registered unconditionally so the published contract is identical across deploy shapes; when the capability behind one did not compose here (authentication disabled, no database, no outbound transport, or the feature switched off) it answers this coded SLC-0012 problem. It is definitive for this deployment: retrying does not help, and the `detail` is deliberately scrubbed (any status >= 500 is). default: content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Error components: schemas: CreateArrangementRequest: additionalProperties: false properties: active: description: Whether the arrangement is active; defaults to true when omitted. examples: - true type: - boolean - 'null' code: description: Card-scheme arrangement code. examples: - VCC maxLength: 10 minLength: 1 type: string role: description: Participant role for this arrangement. examples: - ACQUIRER minLength: 1 type: string required: - code - role type: object ArrangementResponse: additionalProperties: false properties: active: description: Whether the arrangement is active. examples: - true type: boolean code: description: Card-scheme arrangement code. examples: - VCC type: string createdAt: description: Creation timestamp (RFC3339 UTC). examples: - '2026-06-15T07:50:00Z' format: date-time type: string id: description: Arrangement id (UUID). examples: - 0190b5a0-0000-7000-8000-0000000000bb type: string participantId: description: Owning participant id (UUID). examples: - 0190b5a0-0000-7000-8000-0000000000aa type: string role: description: Participant role for this arrangement. examples: - ACQUIRER type: string updatedAt: description: Last-update timestamp (RFC3339 UTC). examples: - '2026-06-15T07:50:00Z' format: date-time type: string required: - id - participantId - code - role - active - createdAt - updatedAt type: object Detail: additionalProperties: false properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). type: string correlationId: description: Request-scoped correlation identifier echoing X-Request-ID. examples: - req-7a3f9c2e type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string upstream: $ref: '#/components/schemas/Upstream' description: >- RFC 9457 extension member: the error a proxied third-party provider reported. Absent unless the emitting service explicitly surfaced one. required: - correlationId type: object ErrorDetail: additionalProperties: false properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' type: string message: description: Error message text type: string value: description: The value at the given location type: object Upstream: additionalProperties: false properties: code: description: The upstream provider's own error code, verbatim. examples: - E4001 type: string message: description: >- The upstream provider's own error message, verbatim (bounded, never its raw response body). examples: - account not found at provider type: string type: object securitySchemes: BearerAuth: bearerFormat: JWT description: JWT bearer token issued by the identity provider. scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.