Create Send Transactions

Create a Single Send Transaction

To create a single send transaction you must provide:

• The source: the instrument from which you are taking funds, this could be either of type managed_cards or managed_accounts,
• The destination: the instrument where the funds will be transferred to, this could either be a managed_card, managed_account or a beneficiaryId
• The destinationAmount.

Retrieve the Status of a Send Transaction

Send transactions are typically executed instantly. However, Weavr may perform risk assessment before executing the transaction. You can receive the status of a send transaction using the API.

info

For a single Send transaction to be processed you need to preform a successful SCA challenge as described here. The challenges /multi/challenges/otp/{channel} endpoint can be used to verify both a single and multiple Send challenges at once by providing the Send ID(s) in the resourceIds field to perform the challenge verification.This endpoint should be used in favour of the deprecated endpoint that can only be used for single OWTs.

GET/sends/{id}Try it

Send States	Description
INVALID	The send transaction has failed initial validation checks.
PENDING_CHALLENGE	The send transaction requires the completion of a transaction confirmation challenge before it can be submitted.
INITIALISED	The initial state of a send transaction when SCA is not required.
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.

POST/sendsTry it

Sends as Bulk Operations

Sends can be created in bulk following the the same process as as other bulk operations, and are executed via the Bulk Process. The OWTs still require a transaction confirmation but they can be grouped together and verified in a single action. See the Bulk Process and specifically Bulk Processing Operations that require a Transaction Confirmation.

Schedule Send Transactions

Single and bulk send transactions can be scheduled to be executed on a future date & time. With every transaction request, you can optionally specify a scheduledTimestamp which contains the date & time in UTC of when the transaction should be executed. Once a transaction is scheduled, and all validations are confirmed, you will receive a webhook with the state of the transaction being Scheduled.

info

Scheduled transactions can be confirmed at any point before their scheduledTimestamp.

Cancel Scheduled Send Transactions

You can cancel scheduled send transactions before the execution time has elapsed. To cancel the transaction you must provide the id of the transaction, and add optionally adding a cancelling reason using this endpoint:

POST/sends/bulk/cancelTry it

info

Transactions that are not in state Scheduled cannot be cancelled. Cancelling a scheduled transaction does not require SCA.

Transaction Confirmation

As per PSD2 requirements, all transactions need to be verified with Strong Customer Authentication (SCA), therefore, once transactions has been submitted, you now need to verify the transactions. Follow this link for more information on how to verify transactions.