§Online Payments
One Payment Intent, from first click to settled funds.
A Payment Intent follows a payment through every state — authentication, authorisation, capture, refund — so your code reacts to clear events instead of guessing. Card data stays in provider-hosted fields, and Strong Customer Authentication is handled for you.
Working in sandbox today. Live processing through authorised partners after review.
Gross volume
€18,642.50
Net after fees
€18,324.40
Payments
143
Next payout
Tomorrow, 10:00
Recent payments
- m.rossi@example.it€120.00Succeeded
- ana.popescu@example.ro€45.50Requires 3-D Secure
- l.martin@example.fr€312.00Refunded €50.00
- j.smith@example.co.uk€89.00Declined
- Integration
- REST API + hosted fields
- Authentication
- 3-D Secure 2 when required
- Amounts
- Integer minor units, ISO currency
- Status
- Working in sandbox
01How a payment moves
Five states, each one observable.
- 01
Create the intent
Your server creates a Payment Intent with an amount, a currency and an Idempotency-Key.
- 02
Collect payment details
Your customer types card details into provider-hosted fields or chooses another method.
- 03
Authenticate when needed
If the issuer asks for Strong Customer Authentication, the intent moves to requires_action and the challenge is shown.
- 04
Authorise and capture
Capture immediately, or authorise now and capture later — fully or partially.
- 05
Record and reconcile
The capture, the fee and the net amount are written to the ledger and later matched to the payout.
02In depth
What is inside a Payment Intent.
- 01
A lifecycle you can rely on
Intents move through explicit states: requires_payment_method, requires_action, processing, requires_capture, succeeded and canceled. Transitions emit webhook events, so you never have to poll.
- Every transition is an event
- Invalid transitions are rejected with invalid_state
- Full history visible in the dashboard
Strong Customer Authentication, handled
In the EEA, most online card payments need SCA under PSD2. VEYRA asks the provider to run 3-D Secure when the issuer requires it, and can request exemptions where the provider supports them.
- Frictionless flow when the issuer allows it
- Challenge flow inside the checkout
- Outcome recorded on the intent
Atelier Lumen
Card · Wallet · Bank transfer
Card details
Entered in provider-hosted fields
Card data never touches VEYRA servers
- 03
Authorise now, capture later
For hotels, rentals and made-to-order goods, place a hold first and capture the final amount when you know it.
- Partial capture
- Cancellation releases the hold
- Expiry reminders before an authorisation lapses
Refunds and disputes
Refund in full or in part, from the API or the dashboard. When a customer disputes a payment, VEYRA opens a case, reserves the amount and walks you through the evidence.
- Partial and multiple refunds
- Dispute evidence checklist
- Reserves shown separately in your balance
- Card country ≠ IP country+18
- 3 attempts in 10 minutes+22
- Email seen before, paid successfully−15
- Amount within customer’s usual range−6
Choose your integration
Four ways in, one ledger underneath.
| Integration | Effort | Card data in your systems | Best for |
|---|---|---|---|
| Payment Links | No code | None | Selling on social, by chat or by email |
| Hosted Checkout | A redirect | None | Shops that want to go live quickly |
| Embedded hosted fields | Front-end + API | None — fields are provider-hosted | Custom checkout inside your site |
| Plugins | Install and configure | None | WooCommerce and Shopify — not yet available |
Every option uses the same Payment Intent and the same webhooks, so you can start simple and move later.
?FAQ
Questions, answered
Which payment methods are available?
In the sandbox you can simulate cards, including 3-D Secure, declines and disputes. Live methods will depend on what our authorised partners support in each country; we will publish the list before launch.
Do I need to be PCI DSS compliant?
Card details are entered in provider-hosted fields and never touch your servers or ours. That keeps your PCI DSS scope as small as possible — typically a self-assessment questionnaire — but the exact obligation depends on your set-up and your acquirer.
What happens if my server times out while creating a payment?
Retry the same request with the same Idempotency-Key. VEYRA returns the original result instead of creating a second payment.
Can I charge in currencies other than euro?
The sandbox accepts 22 currencies, each with its correct number of decimal places. Live currencies will depend on partner coverage.
Take your first test payment in minutes.
Use card 4242 4242 4242 4242 with any future expiry date and any CVC.