How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Veem

Veem payment-controller API

Payment Controller

Documentation Provider Profile APIs.io OpenAPI GitHub

Veem payment-controller API is one of 14 APIs that Veem publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include payment-controller. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 7 paths, and defines 45 schemas. It is described by OpenAPI 3.0.0, at version v1.2.1.

Requests are made against a single base URL, //sandbox-api.veem.com.

7 operations 7 paths 45 schemas 1 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
v1.2.1
Base URL
https://api.veem.com
Resource Areas
1

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 1 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

payment-controller 7

Payment Controller

POST
/veem/v1.2/payments/{paymentId}/approve
approvePayment
approvePaymentUsingPOST_2 1 param → 200400401403404500
POST
/veem/v1.0/payments/cryptowallet/payin
Create a Crypto Wallet pay-in
createCryptoWalletPayin 1 param body → 201400401403404500
POST
/veem/v1.0/payments/cryptowallet/payout
Create a Crypto Wallet payout
createCryptoWalletPayout 1 param body → 201400401403404500
POST
/veem/v1.2/payments
createPayment
createPaymentUsingPOST_2 body → 200201400401403404500
GET
/veem/v1.2/payments/{paymentId}
getPayment
getPaymentUsingGET_2 1 param → 200400401403404500
POST
/veem/v1.0/payments/wallet/addFunds
walletAddFunds
walletAddFundsUsingPOST body → 200201400401403404500
POST
/veem/v1.0/payments/wallet/withdraw
walletWithdraw
walletWithdrawUsingPOST body → 200201400401403404500

Schemas 45

The contract defines 45 schemas that model the data the API accepts and returns. The most detailed are InternalExtraInfoDTO (114 properties), FinancialExtraInfoDTO (114 properties), PaymentResponse (33 properties), PublicBankAccountRequest (30 properties). Each schema is shown below with its type and property counts.

PaymentResponse
object
33 properties 8 required
WalletWithdrawRequest
object
2 properties
PaymentRequest
object
6 properties 5 required
FundingMethod
object
2 properties 2 required
DefaultMethod
object
3 properties
SimpleAccountCryptoWallet
object
Account information for a party involved in a crypto wallet payment.
21 properties 9 required
PaymentApprovalRequest
object
2 properties
JSONObject
object
ManagingPartnerInfo
object
Managing partner information for an account.
2 properties
ErrorResponse
object
4 properties 3 required
ExchangeRateResponseCryptoWallet
object
Exchange rate details for a crypto wallet payment.
8 properties 7 required
LatestCreditDebitResponse
object
3 properties
UserApprovalInfoResponse
object
5 properties
BusinessAddressRequestCryptoWallet
object
Business or individual address details used by crypto wallet endpoints.
7 properties 4 required
LatestCreditDebitErrorResponse
object
2 properties
PaymentAttributesRequest
object
1 property
ContactBusinessRequest
object
3 properties 3 required
PublicBankAccountRequest
object
Bank account details for a payment party.
30 properties
PaymentApprovalResponse
object
4 properties
PublicInvoiceResponseCryptoWallet
object
Payment details returned when creating a crypto wallet payout or pay-in.
30 properties
FeeInformationResponse
object
2 properties
FileAttachment
object
3 properties 3 required
InternalExtraInfoDTO
object
Internal extra information associated with a payment.
114 properties
PushPaymentInfoResponse
object
13 properties
LatestDebitFinancialTxnResponse
object
6 properties
FinancialExtraInfo
object
Additional financial information associated with an invoice.
2 properties
PayoutRequest
object
Request payload for creating a crypto wallet payout.
4 properties
AddressDTO
object
Address details for a payment party or bank.
11 properties
SimpleAccount
object
8 properties 8 required
CardDetailsCryptoWallet
object
Card details associated with a crypto wallet payment.
3 properties
ExchangeRateResponse
object
8 properties 7 required
PayerInfoResponse
object
4 properties
FinancialExtraInfoDTO
object
Internal additional financial information for a payment.
114 properties
PayinRequest
object
Request payload for creating a crypto wallet pay-in.
9 properties
FinancialExtraInfoRequest
object
Additional custom information associated with a request.
1 property
AddWalletFundsRequest
object
3 properties
LatestCreditFinancialTxnResponse
object
7 properties
BusinessAddressRequest
object
6 properties 5 required
LatestFinancialTxnResponse
object
4 properties
FundingMethodCryptoWallet
object
Funding method details for a crypto wallet payment.
7 properties
AlignMonetaryAmountCryptoWallet
object
Monetary amount including crypto currency codes, used by crypto wallet endpoints.
2 properties
ContactBusinessRequestCryptoWallet
object
Business or individual contact details used by crypto wallet endpoints.
8 properties 4 required
PayeeInfoResponse
object
4 properties
AlignMonetaryAmount
object
2 properties
SimpleAccountRequest
object
Account information for the party associated with a pay-in.
14 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

veem-payment-controller-api-openapi.yml Raw ↑

Other APIs Veem publishes across the network.

Veem attachment-controller API
AE Profile APIs.io
Veem bank-account-controller API
AE Profile APIs.io
Veem beneficial-owner-information-controller API
AE Profile APIs.io
Veem claimless-payment-controller API
AE Profile APIs.io
Veem contact-controller API
AE Profile APIs.io
Veem crypto-wallet-controller API
AE Profile APIs.io
Veem customer-controller API
AE Profile APIs.io
Veem exchange-rate-controller API
AE Profile APIs.io
Veem invoice-controller API
AE Profile APIs.io
Veem meta-controller API
AE Profile APIs.io
Veem open-account-controller API
AE Profile APIs.io
Veem wallet-controller API
AE Profile APIs.io
#payment-controller
← Back to V APIs
API Details
ID
veem:veem-payment-controller-api
Base URL
https://api.veem.com
Docs
https://developer.veem.com
Provider
Veem
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=veem-payment-controller-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/veem-payment-controller-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Veem payment-controller API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.