Getting started
Discover

EV Charging

Discover our unattended POS solution for the ev market
Our solutions

CCV Terminal

Integrate with a CCV Terminal

SoftPOS

Turn your own device into a payment terminal

CCV Online Payments

Accepting online payments in your platform without technical knowledge
Connect to the CCV Platform

Integrate our products into your software. Let's make payment happen together!
Look at all the possibilities
Documentation

Return to solutions

Introduction
Attended terminals
- Aborting
  - F1a regular abort by merchant
  - F1b failing abort by merchant
  - F1d hammering abort by merchant
- Allowed amounts
  - S1a transaction with amount zero
  - S1b transaction with negative amount
  - S1c transaction with highest possible amount
  - S1d over amount transaction
- Connection lost
  - Q1b manual transaction recovery
  - Q1c ethernet connection with its fails
  - Q1f device unavailable
  - Q1g terminal not responding
  - T1a automatic transaction recovery
- E journal
  - M1a store e journal
  - M2a ecr pos print journal receipts
  - M3a ecr pos storing journal receipts
- Reprint ticket
  - L1a reprint ticket
  - L1b reprint ticket declined transaction
  - L2a reprint ticket no printer available
  - L2b reprint ticket declined transaction no printer available
- Tickets
  - U1a request for identification
  - U1b request for signature
  - U1c request for signature and identification
  - U1d failing transaction no receipt
  - U1e split payment
- Time out
  - R1a time out on presenting a card
  - R1b time out during pin entry
- Transactions
  - C1a happy flow
  - C1b happy flow contactless
  - C1d happy flow magnetic stripe
  - C1e declined transaction by host
  - C1e transaction aborted by cardholder
  - C1f absence of thousand separator
  - C1g cashier display messages
- Validation
  - H1a too many fingers
  - H1b not removing card
  - H2a power loss or closing of ecr pos during transaction
Unattended terminals
- User guidance
  - C1 successful payment
  - C2 next cardholder
  - C3 abort on pin entry
  - C4 time out during pin entry
  - C5 no amount
  - C6 language selection
  - C7 amount to authorise
  - C8 available funds
- Device selection
  - D1 device selection
  - D2 invalid device
  - D3 charger selection abort
  - D4 no charger selected
  - D5 authorisation no free devices
- Product delivery
  - E1 product selection
  - E2 enabled products
  - E3 invalid product entered
  - E4 product selection aborted
  - E5 no product selected
  - E6 max delivery time
  - E7 abort session
  - E8 abort by pos
  - E9 not started charging in time
  - E10 take more fuel avf
  - E11 multiple sessions mixed
  - E12 postpone cfa new card
  - E13 abort session on card reinsert
- Receipts
  - F1 cardholder receipt info
  - F2 cardholder receipt retrieval
  - F3 reprint ticket
  - F4 f8 ticket printing
  - F9 tracking token deleted
  - F10 printer paper low
  - F11 card payment erased from storage
  - F12 ereceipt received
  - F13 ereceipt failure
- Transaction limit handeling maestro
  - G1 maestro card payment 1 euro
  - G2 maestro card payment 30 euro
  - G3 maestro card payment 60 euro
  - G4 maestro card payment 500 euro
- Transaction limit handeling mastercard
  - H1 mastercard card payment 1 euro
  - H2 mastercard card payment 30 euro
  - H3 mastercard card payment 60 euro
  - H4 mastercard card payment 500 euro
- Mifare handling
  - I1 happy flow mifare
  - I2 unknown mifare card
  - I3 no mifare card presented
  - I4 mastercard presented
- Card circuits
  - L1 available card circuits
- Reconciliation
  - M1 reconciliation as function
  - M2 reconciliation by new shiftnumber
  - M3 pos trigger reconciliation
- Journal
  - N1 journal accessible by authorized employees
  - N2 journal cannot be altered
- Exception flows
  - O1 unknown card session
  - O2 maximum time out
  - O3 device unavailable
  - O4 time out cardtype fallback
  - O5 time out on presenting card
  - O6 app stability
  - O7 automatic startup
  - O8 sleep mode not supported
  - O9 sleep mode supported
- Recovery
  - X1 recovery after communication failure
  - X2 recovery after ccv component update
  - X3 recovery after 24 hour reboort
  - X4 recovery after ccv fusion client restart
  - Y1 recovery after power failure with no battery backup
  - Y2 recovery after power failure with battery backup
SoftPOS
- Success scenarios
  - Installation success
  - Payment success
- Failed scenarios
  - Installation ccv softpos app not installed
  - Payment declined
  - Payment ccv softpos app closed during payment
  - Payment ccv softpos app killed during payment
  - Payment ccv softpos app not installed anymore
- Other scenarios
  - Data cleared

What's on this page

Test Id: SP001

SoftPOS Certification Tests / Success Scenarios / Installation Success - SoftPOS Certification Test

Test Id: SP001

Objective

Get the CCV SoftPOS app in an installed status so that your POS (Point of Sale) app is ready perform a SoftPOS payment.

Preparation

CCV SoftPOS app installed (Demo Build)

Execution

POS app starts installation process
- POS makes an API Request to CCV Payment API to retrieve an installationPayload
- See Installation Request
POS app opens CCV SoftPOS app automatically
- POS app uses SDK
  - Start Installation including the received installationPayload (via installTerminal method)
- POS app uses Deeplink
  - Start Installation including the received installationPayload
CCV SoftPOS app executes installation
CCV SoftPOS app opens POS app automatically

Expected result

Step 4: POS app shows installation was successful.
- See Installation

Go to

Home
Documentation

Cookies Privacy Statement