# Transaction

This section provides the **Transaction** endpoints required to manage and operate the full lifecycle of resources within the ViaBlocks platform. <br/> These endpoints are designed for secure, auditable, and scalable server-to-server integrations, and support core business operations and compliance workflows.

## /transaction/create

 - [POST /transaction/create](https://docs2-viablocks.viamericas.io/apis/outbound/transaction/paths/~1transaction~1create/post.md): ## Purpose
Creates a new outbound cross-border money transfer and registers it in the ViaBlocks platform.

This request defines the sender, beneficiary, transaction details (amounts, currencies, destination), and the selected funding method.

## When to use
Use this endpoint to initiate a new transaction when you are ready to submit:
- Sender onboarding details (KYC/AML fields)
- Beneficiary details and payout configuration
- Origination and delivery amounts/currencies
- Funding configuration (cash or remote payment)

## What happens next
Next steps depend on the funding method:
- Cash funding: Transaction may proceed directly into processing (partner-dependent).
- Remote payment funding: Transaction is created in a pending funding state. The sender must complete payment remotely and the transaction will not proceed until funding and risk/compliance review are completed.

## Authentication
Requires x-client-id and x-secret-key headers.

## Notes
- Request validation is enforced for formats, allowed values, corridor rules, and compliance requirements.
- For the remote payment flow, refer to: ../guides/remotepayment.md

## Common errors
- 400 Validation errors (missing/invalid fields)
- 401 Invalid credentials
- 404 Sender/beneficiary linkage issues (when applicable)
- 422 Business-rule rejection (e.g., credit limit)
- 500 Internal error

## /transaction/status

 - [GET /transaction/status](https://docs2-viablocks.viamericas.io/apis/outbound/transaction/paths/~1transaction~1status/get.md): ## Purpose
Retrieves the latest status and processing details for a previously created transaction.

## When to use
Use this endpoint to:
- Poll for lifecycle updates (funding confirmation, compliance holds, payout progression)
- Display current transaction state in your UI or partner system
- Retrieve hold reasons and required documents (when applicable)

## Authentication
Requires x-client-id and x-secret-key headers.

## How to identify the transaction
Provide the uuid query parameter. The uuid is returned by /transaction/create.

## Notes
- Responses may include holds and requiredDocumentList when compliance or operational review is required.
- Status values reflect internal processing and payout execution steps.

## Common errors
- 400 Missing/invalid uuid
- 401 Invalid credentials
- 404 Transaction not found
- 500 Internal error