> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/marqeta.md).

# Marqeta

Issue cards, manage spending controls, and fund accounts with Marqeta.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication   |
| --------- | ---------------- |
| Marqeta   | API key or token |

#### Marqeta

Connect to Marqeta card issuing with program-specific admin credentials.

**Set up in Marqeta**

1. Prepare the Marqeta account or service that the workflow will access. Grant access to the required resources and operations.
2. **Marqeta API base URL:** Use the exact Marqeta program URL ending in /v3. Do not construct a production URL from a program name.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Marqeta**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field        | Required                 | What to enter                                                                                                                                    |
| -------------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| Marqeta API base URL | Optional / as applicable | Use the exact Marqeta program URL ending in /v3. Do not construct a production URL from a program name.                                          |
| Application token    | Yes                      | Your Marqeta application token, used as the HTTP Basic username. [Provider instructions](https://www.marqeta.com/docs/core-api/authentication).  |
| Admin access token   | Yes                      | Your Marqeta admin access token, used as the HTTP Basic password. [Provider instructions](https://www.marqeta.com/docs/core-api/authentication). |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Marqeta** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### List transactions

Review Marqeta card transactions for monitoring and reconciliation.

**Inputs**

| Field                | Type            | Required | Description                                                                                               |
| -------------------- | --------------- | -------- | --------------------------------------------------------------------------------------------------------- |
| Maximum transactions | integer         | No       | Maximum number of transactions to return. Minimum: 1. Maximum: 2000. Default: 100.                        |
| Start index          | integer         | No       | Resume listing from this result index. Minimum: 0. Default: 0.                                            |
| Start date and time  | datetime        | No       | Only include transactions on or after this time.                                                          |
| End date and time    | datetime        | No       | Only include transactions before this time.                                                               |
| Transaction type     | string          | No       | Filter by a Marqeta transaction type.                                                                     |
| Transaction state    | select (string) | No       | Filter transactions by processing state. Available values: Pending, Cleared, Completion, Declined, Error. |
| Cardholder           | select (string) | No       | Only include transactions for this cardholder. Options load from the selected connection.                 |
| Business             | select (string) | No       | Only include transactions for this business. Options load from the selected connection.                   |
| Acting cardholder    | select (string) | No       | Only include transactions initiated by this acting cardholder. Options load from the selected connection. |
| Card                 | select (string) | No       | Only include transactions for this card. Options load from the selected connection.                       |

**Outputs**

| Field            | Type          | Description                                                        |
| ---------------- | ------------- | ------------------------------------------------------------------ |
| Transactions     | object\_array | Transactions with their amount, state, type, cardholder, and card. |
| Next start index | integer       | Index to use for the next batch, when more results exist.          |

#### Create velocity control

Set an amount or usage limit for a cardholder, card product, or program.

**Inputs**

| Field               | Type            | Required | Description                                                                                                                                                      |
| ------------------- | --------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Amount limit        | number          | Yes      | Maximum cleared amount allowed during the selected window. Minimum: 0.                                                                                           |
| Currency            | string          | Yes      | Currency used for the amount limit. Default: USD.                                                                                                                |
| Limit window        | select (string) | Yes      | Time period over which spending is limited. Available values: Day, Week, Month, Lifetime, Transaction.                                                           |
| Usage limit         | integer         | No       | Maximum number of uses during the window. Minimum: -1. Maximum: 100.                                                                                             |
| Apply to            | select (string) | Yes      | Choose whether this limit applies to one cardholder, one card product, or the whole program. Available values: Cardholder, Card product, Program. Default: USER. |
| Cardholder          | select (string) | No       | Apply the control to one cardholder. Options load from the selected connection.                                                                                  |
| Card product        | select (string) | No       | Apply the control to every card in a card product. Options load from the selected connection.                                                                    |
| Control description | string          | No       | Explain what this control restricts for later monitoring.                                                                                                        |
| Control token       | string          | No       | Stable identifier used to make retries safe.                                                                                                                     |

**Outputs**

| Field            | Type   | Description                           |
| ---------------- | ------ | ------------------------------------- |
| Velocity control | object | The created Marqeta velocity control. |

#### Fund GPA order

Load funds onto a cardholder or business general purpose account.

**Inputs**

| Field               | Type            | Required | Description                                                                                                     |
| ------------------- | --------------- | -------- | --------------------------------------------------------------------------------------------------------------- |
| Account holder type | select (string) | Yes      | Choose whether funds go to a cardholder or business GPA. Available values: Cardholder, Business. Default: USER. |
| Cardholder          | select (string) | No       | Cardholder whose GPA receives the funds. Options load from the selected connection.                             |
| Business            | select (string) | No       | Business whose GPA receives the funds. Options load from the selected connection.                               |
| Funding source      | select (string) | Yes      | Funding source used for this load. Options load from the selected connection.                                   |
| Amount              | number          | Yes      | Amount to load onto the GPA.                                                                                    |
| Currency            | string          | Yes      | Currency of the funding order. Default: USD.                                                                    |
| Order token         | string          | Yes      | Unique identifier that prevents duplicate funding on retries.                                                   |
| Memo                | string          | No       | Optional note describing the funding order.                                                                     |

**Outputs**

| Field     | Type   | Description                      |
| --------- | ------ | -------------------------------- |
| GPA order | object | The submitted GPA funding order. |

#### Create user

Create an individual cardholder in a Marqeta program.

**Inputs**

| Field                | Type    | Required | Description                                                       |
| -------------------- | ------- | -------- | ----------------------------------------------------------------- |
| First name           | string  | Yes      | Cardholder's legal first name.                                    |
| Last name            | string  | Yes      | Cardholder's legal last name.                                     |
| Email                | string  | No       | Cardholder's email address.                                       |
| Phone number         | string  | No       | Cardholder's phone number.                                        |
| Show advanced fields | boolean | No       | Show optional KYC and residential address fields. Default: false. |
| Birth date           | string  | No       | Cardholder's date of birth when required for KYC.                 |
| Street address       | string  | No       | Primary residential street address used for KYC.                  |
| City                 | string  | No       | City for the residential address.                                 |
| State or region      | string  | No       | State or region for the residential address.                      |
| Postal code          | string  | No       | Postal code for the residential address.                          |
| Country code         | string  | No       | Country of the residential address. Default: US.                  |
| User token           | string  | No       | Stable identifier for the new cardholder.                         |

**Outputs**

| Field | Type   | Description             |
| ----- | ------ | ----------------------- |
| User  | object | The created cardholder. |

#### Create card

Issue a new card for an existing cardholder.

**Inputs**

| Field        | Type            | Required | Description                                                                        |
| ------------ | --------------- | -------- | ---------------------------------------------------------------------------------- |
| Cardholder   | select (string) | Yes      | Cardholder who will own the card. Options load from the selected connection.       |
| Card product | select (string) | Yes      | Card product that defines the new card. Options load from the selected connection. |
| Card token   | string          | No       | Stable identifier for the new card.                                                |

**Outputs**

| Field | Type   | Description                            |
| ----- | ------ | -------------------------------------- |
| Card  | object | The new card's non-sensitive metadata. |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/marqeta.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
