Build payments into any POS.
One open platform for on-terminal apps, external POS over the local network, and cloud integrations. Guides, an API reference, sample code and an AI agent skill to get you live faster.
CodePay SaaS Suite is PCI DSS v4.0 certified. POST /api/entry/wisehubcloudpayorder { "app_id": "<APP_ID>", "merchant_no": "<MERCHANT_NO>", "method": "wisehub.cloud.pay.order", "sign_type": "RSA2", "timestamp": "<13-digit ms>", "biz_data": { "device_sn": "<TERMINAL_SN>", "order_amount": "<AMOUNT>", "trans_type": "<TRANS_TYPE>" } }
200 OK { "trans_status": 9 } // pushed, awaiting payment on the terminal
Pick the path that fits your product.
Every path ends at CodePay Register on a certified terminal, so card data never touches your POS.
Run your app on a CodePay terminal.
Your Android POS app runs on the terminal and calls Register through intent-based payment APIs, with access to terminal hardware.
Android POS apps that want a single device at checkout.
- Android SDK and demo app on GitHub
- Uses terminal hardware such as the printer and scanner
- No network hop between POS and payment
Connect an external POS over WLAN.
Your POS on separate hardware talks to the terminal over the store network using WebSocket.
Windows, Android or iOS POS apps in stores with stable Wi-Fi.
- Assign the terminal a DHCP reservation or static IP
- Set DHCP leases to 24 hours or longer
- Works across Windows, Android and iOS
Send orders from your backend.
Your web POS or backend pushes payment orders to the terminal through the CodePay Cloud API over HTTP and MQTT.
Web POS and multi-location software with reliable internet.
- REST API, independent of terminal type
- RSA2-signed requests
- Recall API to resolve timeouts without double charging
From test account to first payment in four steps.
Ask your company's PayPilot admin for access, or contact CodePay if you don't have one yet.
Create a test merchant account, then a Payment App ID so CodePay can verify your POS app.
Test merchant guide ↗Integrate on the terminal, over the local network, or through the cloud.
Compare paths ↗Run approvals, declines and timeouts with UAT test cards and the test scenarios.
Test cards ↗Fourteen endpoints. One signed request format.
Point of sale, hosted checkout, reference transactions and settlement, all through the Cloud API.
Every request is signed with RSA2 and carries your App ID.
Requests include a 13-digit timestamp and must be within 15 minutes of server time.
Merchant Hosted Checkout encrypts card data with the gateway public key before it is sent.
If a response never arrives, call Recall before retrying to avoid duplicate charges.
Let your coding agent write the integration.
The CodePay agent skill teaches AI coding tools our protocol, and tells them to check the latest spec on developer.codepay.us before writing code.
# Claude Code: install the CodePay skill git clone https://github.com/codepay-us/integrating-agent-skill \ ~/.claude/skills/integrating-codepay-payments # then, in your project /integrating-codepay-payments Add CodePay card payments to my Windows cashier app over the local network.
Clone the repo into your skills folder. It is picked up automatically and stays current with git pull.
Download the repo as a ZIP and upload it as a skill.
Add SKILL.md and codepay-protocol-reference.md as rules or system context.
Test every outcome before you go live.
Talk to the engineers who built it.
Every ISO and ISV partner works directly with our technical, product and operations teams.
API releases and documentation changes are posted on the developer site.
Request developer access.
Tell us about your POS and the integration path you're considering. We'll set up test credentials and evaluation devices.