Requirements

Integration requirements checklist

The following are mandatory requirements your integration must meet before certification. Optional items are marked.

Branding

• Pairing screen displays the name "Simple Cloud Integration"
• Pairing screen displays the SCI logo

Pairing UI

• Unpaired state shows Pairing Code field and optional Pairing Nickname field
• Pairing flow includes a Test button to check the pairing status
• Pairing flow includes a Cancel button
• Paired state shows success message, Pairing Nickname and Pairing ID
• Unpair button present for each pairing record
• All error states handled (invalid code, connectivity failure, externally unpaired)
• Pairing instructions displayed (optional)

Transactions

• No active pairing error (NO_ACTIVE_PAIRINGS_FOUND) handled and displayed
• Action Framework drives the POS UI rendering based on message & pos_instructions fields
  • All element types supported (text, button, input, image)
• Handling of Approved, Declined & Cancelled transactions
• Signature flow handled (POS based handling is mandatory, terminal based handling is optional)
• Merchant and customer receipts printed, displayed or stored
• Terminal busy error (TRANSACTION_REFUSED) handled and displayed

Transaction recovery

• Device not connected error (DEVICE_NOT_CONNECTED) handled and displayed
• Override flow implemented — merchant can confirm transaction outcome when the POS is unable to get updates from the SCI API

Security

• Pairing API Secret Key is not visible, configurable, or editable in the POS UI
• Pairing API Secret Key is securely stored