Axiym

Store a payment data map

Validates and stores rules for mapping a complete payment object: payment and party fields, document connections, reviewed value translations, sender handling, and amount resolution. Download or copy the definition from Smart Payload Mapping, then submit it as definition alongside a name. Access is determined by your credentials.

Storage validates the schema version, safe paths, known targets, unique field sources and targets, compatible array associations, document connection rules, and allowed translation outputs. Value rules must match a configured field or document-type connection and must not redefine an existing Axiym code. Invalid or conflicting rules are rejected with HTTP 422. Actual source data, document matches, and corridor requirements are validated when the map is used.

New maps have status ACTIVE. The response includes paymentDataMapId and contentHash. Definitions are immutable: store changed rules as a new map and use its new identifier.

AuthorizationBearer <token>

In: header

Header Parameters

X-Request-Id?string

Optional request identifier for tracing and support. A UUID is recommended. Axiym echoes it in X-Request-Id, or generates one when omitted.

Formatuuid
Idempotency-Key*string

Identifies one state-changing operation. Retry with the same endpoint, request body, and key to receive the original result without repeating the operation. Use a new key for a new operation, including confirmation after creation.

Lengthlength <= 255

Request Body

application/json

Name, optional description, and mapping definition to store.

name*string

Name used to identify the stored map in your integration.

Length1 <= length <= 120
description?string

Optional note describing the source structures or integration that uses this map.

Lengthlength <= 500
definition*PaymentDataMapDefinition

Reusable rules that transform your complete payment JSON into the Axiym payout input. Field paths are relative to the payment object sent to POST /payouts/mapped. The definition stores rules and reviewed labels, not payment records or file content. Definitions are immutable; store changed rules as a new map. Unsupported schema versions are rejected.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json