GET /api/v1/payments
Operation: getPayments. Documented HTTP responses: 200, 400, 401.
Field-level payment API reference. Public OpenAPI version 1.0.7009, checked .
This extract describes the published contract, not a production test or a guarantee that every operation is enabled for your account.
Read the publisher’s complete reference. Confirm the applicable contract version before implementation.
The listed payment operations use Authorization: Bearer <SHOP_API_KEY>. Obtain the key for your authorised environment; keep it on your server. No key prefix or rotation grace period is specified here.
https://psp-demo.viabanking.comhttps://psp.viabanking.comAPI paths start with /api/v1/. Specification version 1.0.7009 and the URL version are different identifiers.
GET /api/v1/paymentsOperation: getPayments. Documented HTTP responses: 200, 400, 401.
POST /api/v1/paymentsOperation: createPayment. Documented HTTP responses: 200, 400, 401.
GET /api/v1/payments/{id}Operation: checkStatus. Documented HTTP responses: 200, 401, 404.
GET /api/v1/payments/{id}/operationsOperation: getOperations. Documented HTTP responses: 200, 401, 404.
POST /api/v1/payment-methods/availableOperation: getPaymentMethod. Documented HTTP responses: 200, 400, 401, 404.
The creation operation describes deposit, payout and refund requests. Confirm permitted payment methods and operations for your account; the path alone does not establish licensed PIS or recurring-payment availability.
idreferenceIdpaymentTypestatedescriptionparentPaymentIdpaymentMethodpaymentMethodDetailsamountcurrencycustomerAmountcustomerCurrencyredirectUrlerrorCodeexternalResultCodeexternalRefscustomerbillingAddressterminalNamereferenceIdparentPaymentIdpaymentTypepaymentMethodamountcurrencydescriptioncustomerbillingAddressreceiverreturnUrlpendingReturnUrlsuccessReturnUrldeclineReturnUrlwebhookUrlwebsiteUrladditionalParameterstimestampstatushasMoreresulttimestampstatusresulttimestampstatuserrormessageerrorspathThese are top-level fields. Read nested schemas, enums and conditional requirements in the complete reference before sending a request. Do not infer that optional fields are unnecessary for every payment method.
GET /api/v1/payments uses offset (default 0) and limit (default 50, range 1–1000). The response includes hasMore. This is not cursor pagination.
Use each operation’s response definitions; the Error schema has top-level fields rather than a nested error.code envelope. An HTTP 200 alone does not establish payment completion or credited funds.
Idempotency-Key scope, retention, retry limits and conflict handling are not established by the inspected contract. After a timeout or ambiguous write, reconcile the original operation before submitting another payment. Do not change a key simply to bypass a conflict. Obtain the supported deduplication procedure before enabling automatic write retries.
The payment request includes webhookUrl and the contract defines WebhookResult with state. The inspected contract does not define a payment.settled event catalogue, HMAC header, retry window or acknowledgement deadline.
Confirm callback authentication, acknowledgement, retries, ordering and duplicate handling with the integration owner. Do not treat an unverified callback or a state name as proof of settlement finality.
The inspected paths do not document generic /accounts, /consents or /banks APIs, recurring mandates, or a C2B credit-matching contract. This does not prove these capabilities are unavailable; request their applicable specification and enabled scope before relying on them.