arvonapayMerchant login ↗
A CLEARER WAY TO OPERATE

Every payment.
A clearer
perspective.

One considered workspace for bank transfers, gateways and merchant operations. Separate flows. Precise access. A connected view.

Open your workspace ↗Explore the API →
Sandbox available · Access by invitation
THE ARVONA VIEW 01 / SANDBOX
↗
01 · CREATEPayment intent

One reference. One request.

✓
ROUTE WITH CONTEXT
⇄
TRANSFER FLOWBank transfer
▦
PAYMENT FLOWGateway
ONE AUDITABLE JOURNEY
02 · RECONCILEA shared source of clarity.

Merchant view + signed notifications

Illustrative sandbox flowBuilt for clarity.
Separate operations.Defined permissions.Currency-aware records.Documented integration.
A WORKSPACE THAT MAKES SENSE

Complex operations.
Thoughtful separation.

Give each team a focused environment while keeping the operational picture connected.

01
BANK TRANSFERS

Room for every
transfer decision.

Keep deposits and withdrawals in a dedicated workspace. Track pending requests, require an independent approver and inspect the full event history.

  • Deposit and withdrawal views
  • Independent withdrawal approval
  • Per-currency financial records
Transfer workspaceSANDBOX
↙
DepositReference · amount · currency
Track
↗
WithdrawalCreated by one · approved by another
Review
A separate path for each direction.
02
GATEWAY OPERATIONS

Connections
with context.

Inspect test payment connections and routing rules without mixing them into your bank transfer workflow. Follow a payment from creation to its terminal result.

  • Dedicated gateway workspace
  • Priority and weighted sandbox routing
  • Explicit test result simulation
Routing perspectiveTEST MODE
Payment intent↓Eligible connection↓Result + ledger + event
Live processing remains disabled.
03
PEOPLE & MERCHANTS

The right view.
For the right person.

Define what a team member can see and do. Give merchants their own portal, scoped records and server-side integration keys.

  • Module and action permissions
  • Merchant-specific access
  • Working-hour restrictions
Access with intentionSCOPED
OperationsViewCreateApprove
ApproverViewCreateApprove
MerchantOwn recordsOther firms
Every request is checked on the server.
CONFIDENCE, BY DESIGN

A deliberate approach
to access and records.

Security controls belong in the workflow, from the first login to the final notification.

01

Two-step authentication

Mandatory authenticator setup, one-use recovery codes and limited sessions.

02

Defined boundaries

Server-enforced permissions, merchant isolation and origin-checked browser requests.

03

Traceable records

Append-only journals, an audit hash chain and independent withdrawal approval.

04

Signed delivery

HMAC-signed events, durable retry records and stable event identifiers.

BUILD WITH ARVONA

Start in the sandbox.
Understand every step.

Clear request examples, a versioned API contract and a practical notification guide.

Read the integration guide ↗
YOUR FIRST REQUEST
POST /v1/payments

{
  "reference": "order-0001",
  "amount": "1250.50",
  "currency": "TRY",
  "method": "BANK_TRANSFER",
  "direction": "DEPOSIT"
}
Sandbox only · Server-side credentials