# Create a send transaction

Sends funds between managed accounts and managed cards belonging to different corporate or consumer identities.

The Send Profile (configured in the Multi Portal) specified determines the behaviour and restrictions of the transaction (for example, fees).

Endpoint: POST /sends
Version: 3.63.5
Security: auth_token, api-key

## Header parameters:

  - `idempotency-ref` (string)
    A unique call reference generated by the caller that, taking into consideration the payload as well as the operation itself, helps avoid duplicate operations. Idempotency reference uniqueness is maintained for at least 24 hours.

## Request fields (application/json):

  - `profileId` (string, required)
    The profile Id which a specific identity, instrument or transaction type is linked to.

Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.

You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.

Profile Ids can be found in the Multi Portal, in the API Credentials page.

  - `tag` (string)
    The tag field is a custom field that can be used to search and filter.

  - `source` (object, required)

  - `source.id` (string, required)

  - `source.type` (string, required)
    Enum: "managed_cards", "managed_accounts"

  - `destination` (any, required)

  - `destinationAmount` (object, required)
    The object representing a monetary amount in a particular currency.

  - `destinationAmount.currency` (string, required)
    The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.

  - `destinationAmount.amount` (integer, required)
    The monetary amount, scaled to the lowest denomination of the currency.

Example, an amount of 1000 for a EUR currency is actually 1000 Euro cents or EUR 10.00.

  - `description` (string)
    The description details that are passed to the beneficiary.

  - `scheduledTimestamp` (string)
    The epoch timestamp at which the transaction is scheduled to be executed.

## Response 200 fields (application/json):

  - `id` (string, required)
    The unique identifier of a send transaction.

  - `profileId` (string, required)
    The profile Id which a specific identity, instrument or transaction type is linked to.

Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.

You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.

Profile Ids can be found in the Multi Portal, in the API Credentials page.

  - `tag` (string)
    The tag field is a custom field that can be used to search and filter.

  - `source` (object, required)
    The source managed account or card from where the funds were sent.

  - `source.id` (string, required)

  - `source.type` (string, required)
    Enum: "managed_cards", "managed_accounts"

  - `sourceFee` (object)
    The object representing a monetary amount in a particular currency.

  - `sourceFee.currency` (string, required)
    The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.

  - `sourceFee.amount` (integer, required)
    The monetary amount, scaled to the lowest denomination of the currency.

Example, an amount of 1000 for a EUR currency is actually 1000 Euro cents or EUR 10.00.

  - `destination` (any)
    The destination managed account or card to where the funds were sent.

  - `destinationAmount` (object, required)
    The amount, in same currency as source and destination, that was sent from the source to the destination instrument.

  - `destinationFee` (object)
    The object representing a monetary amount in a particular currency.

  - `transactionAmount` (object, required)
    The object representing a monetary amount in a particular currency.

  - `description` (string)
    The description details that are passed to the beneficiary.

  - `state` (string, required)
    The state of the send transaction, as follows:
 - INVALID: The send transaction has failed initial validation checks. 
 - INITIALISED: The initial state of a send transaction when SCA is not required.
 - PENDING_CHALLENGE: The send transaction requires the completion of a transaction confirmation challenge before it can be submitted.
 - PENDING: The send transaction has exceeded the destination limit and is pending treasury approval.
 - APPROVED: The send transaction that was submitted has been approved.
 - COMPLETED: The requested funds have been sent from the source instrument.
 - REJECTED: The send transaction that was submitted was rejected.
 - FAILED: There was an issue with the send transaction, and the transaction has failed.
 - RETURNED: The send transaction has been returned to the sender.
 - SCHEDULED: The send transaction will be executed at the scheduled time.
 - CANCELLED: The scheduled send transaction has been cancelled.
    Enum: "INVALID", "INITIALISED", "COMPLETED", "REJECTED", "FAILED", "PENDING", "PENDING_CHALLENGE", "APPROVED", "RETURNED", "SCHEDULED", "CANCELLED"

  - `challengeExemptionReason` (string)
    The Reason the transaction was exempted from SCA verification
    Enum: "LOW_VALUE", "TRUSTED_BENEFICIARY"

  - `creationTimestamp` (integer, required)
    The time when the transaction was created, expressed in Epoch timestamp using millisecond precision.

  - `scheduledTimestamp` (string)
    The epoch timestamp at which the transaction is scheduled to be executed.

  - `executionTimestamp` (string)
    The epoch timestamp at which the transaction was executed, transitioning to a final state such as COMPLETED, REJECTED, or FAILED.

  - `cancellationReason` (string)
    The reason the scheduled transaction was cancelled.

## Response 400 fields (application/json):

  - `message` (string)
    When present helps to identify and fix the problem.

  - `syntaxErrors` (object)
    Is returned as part of an HTTP error response whenever a syntax error is detected. A list of the fields together with their syntax error will be provided.

  - `syntaxErrors.invalidFields` (array)

  - `syntaxErrors.invalidFields.params` (array)

  - `syntaxErrors.invalidFields.fieldName` (string)

  - `syntaxErrors.invalidFields.error` (string)
    Enum: "REQUIRED", "HAS_TEXT", "REQUIRES", "SIZE", "RANGE", "IN", "NOT_IN", "REGEX", "EXACTLY", "AT_LEAST", "AT_MOST", "ALL_OR_NONE"

## Response 409 fields (application/json):

  - `errorCode` (string, required)
    Enum: "PROFILE_INACTIVE", "MODEL_CONSTRAINTS_VIOLATED", "INTERCEPTOR_DENIED_TRANSACTION", "INSTRUMENT_DENIED_TRANSACTION", "FOREX_TRADE_DENIED_TRANSACTION", "CURRENCY_MISMATCH", "SOURCE_INSTRUMENT_BLOCKED", "DESTINATION_INSTRUMENT_BLOCKED", "SOURCE_NOT_FOUND", "DESTINATION_NOT_FOUND", "FEE_NOT_CONFIGURED_FOR_CURRENCY", "DESTINATION_LIMIT_EXCEEDED", "FUNDS_INSUFFICIENT", "AMOUNT_INVALID", "SOURCE_CANNOT_BE_DEBIT_MODE_CARD", "DESTINATION_CANNOT_BE_DEBIT_MODE_CARD", "SEND_TO_INSTRUMENT_UNSUPPORTED", "SOURCE_INSTRUMENT_DESTROYED", "DESTINATION_INSTRUMENT_DESTROYED", "SOURCE_AND_DESTINATION_MUST_BE_DIFFERENT", "IDENTITY_KYC_LEVEL_STEPUP_REQUIRED", "DESTINATION_BELONGS_TO_SAME_IDENTITY", "SOURCE_AND_DESTINATION_MUST_BE_IN_SAME_PROGRAMME", "BENEFICIARY_NOT_FOUND", "BENEFICIARY_TYPE_INVALID", "PROFILE_NOT_FOUND", "SCHEDULED_TIMESTAMP_INVALID", "DESTINATION_FEE_EXCEEDS_TRANSACTION_AMOUNT"

## Response default fields (application/json):

  - `code` (string)

  - `message` (string)


## Response 401 fields

## Response 403 fields

## Response 429 fields

## Response 500 fields

## Response 503 fields