1 | Obtain Operator ID and API key from CloudAggregator. | Contact your integration manager. |
2 | Register accepted currencies with CloudAggregator. | Provide a full list of ISO 4217 codes. |
3 | Provide wallet endpoint URL to CloudAggregator. | Must be HTTPS with valid TLS 1.2+ certificate. |
4 | Configure IP allowlist on your firewall for CloudAggregator callback IPs. | Request current IP list from your integration manager. |
5 | Implement X-CA-Signature validation on all incoming callbacks. | Use the shared secret provided during onboarding. |
6 | Implement GetAccount endpoint. | Handle all required response fields. |
7 | Implement GetBalance endpoint. | Return real_balance, bonus_balance, and balance. |
8 | Implement Wager endpoint with idempotency. | Test duplicate request handling. |
9 | Implement Result endpoint. | Must accept results for expired sessions (never return 1000). |
10 | Implement WagerAndResult endpoint. | Required for Rummy, Bingo, Lottery. |
11 | Implement Rollback endpoint. | Required for Slots, Live Casino. Handle by transaction_id alone. |
12 | Implement Jackpot endpoint. | Required for Bingo and progressive slot titles. |
13 | Implement Rollback on Result (reversewin) endpoint. | Required for Sports Book. |
14 | Test all error codes and verify correct HTTP 200 with appropriate code in body. | All responses return HTTP 200; error is in the code field. |
15 | Test idempotency for all transaction types. | Send same request twice; verify identical response. |
16 | Implement UKGC reality check parameters. | Required for UKGC-licensed Operators. |
17 | Verify responsible gaming limit enforcement in Wager endpoint. | Test codes 1006, 1019, 1035. |
18 | Complete CloudAggregator UAT (User Acceptance Testing) in the staging environment. | Coordinate with your integration manager. |
19 | Complete production go-live checklist with CloudAggregator. | Final sign-off required before go-live. |