# Submit Transaction

***

### Description:

This endpoint is designed to create a transaction, withdrawal, and invoice with a status set to pending. It initiates the transaction process and ensures that all the relevant details are captured accurately.

**Mode:**

`POST`

#### Node:

```bash
/third-party-service/submit-transaction
```

<mark style="color:green;">`POST`</mark> `/third-party-service/submit-transaction`

Create a transaction, withdrawal, and invoice during pending status

#### Headers

| Name                                            | Type                                                                                                                                                 | Description                                                    |
| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
| API-Key<mark style="color:red;">\*</mark>       | String                                                                                                                                               | Your API key for authentication.                               |
| API-Secret<mark style="color:red;">\*</mark>    | String                                                                                                                                               | Your API secret for enhanced security.                         |
| Authorization<mark style="color:red;">\*</mark> | eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VybmFtZSI6IkBub3ZhNDciLCJzdWIiOjExNywiaWF0IjoxNjg5MDk1MDI3fQ.0BHv\_jc6etSqAuTinoKxSiXnmrC4XLfiezRQZbNG8cA | Access token obtained from the KYC Lite process. Example token |

#### Request Body

| Name                                               | Type                                   | Description |
| -------------------------------------------------- | -------------------------------------- | ----------- |
| "withdrawlPhone"<mark style="color:red;">\*</mark> | "+584241256099"                        |             |
| "businessInitTx"<mark style="color:red;">\*</mark> | "24d00b1f-3d3d-4139-ad2c-479f3fc00573" |             |
| "BusinessTo"<mark style="color:red;">\*</mark>     | "10"                                   |             |
| "exchangeId"<mark style="color:red;">\*</mark>     | "1b59639d-093b-4b3a-b82c-bb0ea57719ca" |             |
| "amount"<mark style="color:red;">\*</mark>         | 0.5                                    |             |
| "typeProcesor"<mark style="color:red;">\*</mark>   | "BANK"                                 |             |

{% tabs %}
{% tab title="202: Accepted " %}

```json
// 
{
  "statusCode": 202,
  "message": "master transaction webview",
  "data": {
    "id": "fcc47165-b296-4545-8576-e3c4dfeeb8a4",
    "invoice": {
      "id": "888c3fb7-f2fb-46a8-bbcd-89a799c3f1e2"
    }
  }
}
```

{% endtab %}
{% endtabs %}

#### Considerations:

After creating a transaction using this endpoint, it's essential to subsequently consult the invoice using the designated API endpoint. Once the invoice is approved, the transaction and withdrawal processes are activated.

IF withdrawal method is through an ATM partner, a QR code will be provided and sent to the individual's `"withdrawlPhone"`

***

**"Pay Out"** - Liquidation process is solidified in our partnerships meetings ensuring we offer a solution that fits your specific needs.

**"Pay In"** - Depending on the country of the requested transaction the user will receive the following response:

* **Brazil** - **QR Code** - when a bank is registered the PIX number as well as the CPF must be identified in order to complete a transaction. The result of the transaction produces a QR code which will be scanned by a PIX account in order to complete the transaction.&#x20;

* **Argentina** - **CVU/CBU account** - When a bank is registered they must confirm the CVU/CBU account or Alias of the individual requesting a transaction. Alfred will display a CVU where the deposit will take place, which will have to come from a CVU/CBU already registered in Alfred pay.&#x20;

* **Mexico** - **'CLABE' account** - CLABE account must be verified with their respective identification documents, transaction produces a reference number which will allow you to identify and complete your transaction.&#x20;

&#x20;Specific Information regarding KYC Documents by country can be found [here](/alfred-integration-docs/welcome/alfred-overview/required-documents-for-kyc-by-country.md).

&#x20;<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://alfred.gitbook.io/alfred-integration-docs/penny-api-general-integration/penny-api-operations/submit-transaction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.