Integration Testing

A few details have to be in place before a payment test can run. Without them, a successful screen or a declined card can be misleading.

1. Device and reader. Tell us the phone or tablet you will use, including whether it is iOS or Android, the OS version, and the reader's Bluetooth model, firmware, and provisioning. Having a device nearby is not enough. A reader that shows up over USB on a computer does not prove it will connect over Bluetooth, or that provisioning is complete, on either platform.
2. App versions. We need the BluePOS Go build and the SDK release for each platform you want tested, along with the full sample projects. Tests should compile against those versions so the operations match what you will ship.
3. Test account. Provide a staging or certification account, the processor route, the app login, and the SDK credentials. The app, the SDK, and the reader need to point at the same [test] environment on every platform under test.
4. Test cards. Provide physical test cards and the approve and decline cases your processor expects. A normal online test-card number cannot exercise chip insert or tap.
5. Payment rules. Confirm the currency, the entry modes you support, and the rules for tipping, capture, refund, and saving a card. Those rules decide which results count as a pass or a fail, and they should be the same on iOS and Android unless you tell us otherwise.
6. How to look up a payment. Provide the server-side lookup or report API, its credentials, and how long a transaction can take to appear. A missing callback is not a failure until that lookup has resolved it by transaction or order reference. To get a single transaction via Bluefin APIs, refer to Getting Transaction Metadata.
7. Retries. Tell us how a request ID maps to the gateway’s external ID, and what happens if the same payment is sent twice. A retry must not create a second charge.
8. Returning to your app. Confirm the callback fields, the timeout rules, and what should happen if the app is closed before BluePOS Go returns. Those details set the expected result on both platforms. They should not be guessed from a sample callback.