Schedule a demo

Docs

One-off payment initiation through licensed PIS providers is live. — viaBanking is a software / Technical Service Provider and Open Banking orchestration layer. Licensed AIS/PIS partners perform regulated actions. viaBanking is not a bank, payment processor or licensed AIS/PIS provider and does not hold or move customer funds. Scheduled, recurring and VRP payments are available only where supported by the selected provider and bank.

Guides and concepts: auth & consent, account data, payments, webhooks and going live. Full endpoint spec in the API Reference.

Get sandbox access Schedule a demo

Guides & concepts

Start with the Quickstart, then move through auth, data, payments and going live. Every concept links inline to its field-level entry in the API Reference.

  • Start here

    Quickstart

    Request sandbox credentials, confirm your enabled payment methods and begin with a read-only request.

    Jump to Quickstart
  • Access

    Auth & consent

    Keep Shop API keys server-side. Confirm the customer consent flow separately for each enabled service.

  • Scope

    Account data

    Current AIS scope is read-only C2B credit verification. Confirm the matching contract, including partial, delayed and unmatched credits, before automating reconciliation.

  • Payments

    Payments

    Follow the published payment request schema and check permitted operations for your account.

  • Async

    Webhooks & statuses

    Confirm callback authentication and delivery semantics before acting on a notification.

  • Reliability

    Errors & retries

    Reconcile ambiguous results before retrying writes; obtain the supported deduplication contract.

  • Sandbox

    Testing

    Agree test cases, fixtures and differences from production with the integration owner.

  • Go live

    Go-live checklist

    Confirm service scope, production access and operational handling before launch.

Three steps to a sandbox request

Request access, confirm the applicable contract and start with a read-only sandbox call.

  1. Request sandbox access

    Contact the integration team for the sandbox account, permitted operations and Shop API key.

  2. Confirm the contract

    Use the public OpenAPI version identified in API Reference. Confirm payment methods, permissions and callback requirements.

  3. Make a read-only request

    Use GET /api/v1/payments on the sandbox server with the sandbox Shop API key. Read the response schema before interpreting the result.

Ship without surprises

Use this checklist after confirming the production scope for your integration. Field-level shapes live in the API Reference.

  1. Confirm production approval, enabled services, provider and account arrangements, and target banks. Keep sandbox-only and roadmap features outside launch scope.
  2. Confirm the production server and credentials with the integration owner; do not assume a key naming convention.
  3. Test payment-state handling and reconcile ambiguous outcomes before retrying writes.
  4. Agree callback authentication, delivery, duplicate handling and acknowledgement requirements.
  5. Confirm rate limits, retry policy and idempotency behaviour from the applicable contract.
  6. Agree monitoring, escalation, reconciliation and rollback procedures.

One integration. Clear specs.

  • Service scope

    Confirm enabled capabilities before implementation

  • 2,500+

    Banks & EMIs in one layer

  • REST + JSON

    Read request and response schemas in API Reference

  • Access on request

    Confirm prerequisites and timing with the integration team

Ready to build? Get sandbox access.

Start with the Quickstart above, then keep the API Reference open beside it.

Get sandbox access Schedule a demo

Updated: