01HPP
Hosted checkout
Fastest route to a secure hosted payment journey.
Lower card-data exposureDeveloper Quickstart
Start in sandbox. Ship with control.
Choose the right integration, test the full payment lifecycle and move to production through a documented activation path.
Payment lifecycleSandbox
- 01Your server creates a signed checkout session
- 02Customer completes the enabled payment journey
- 03SenroPay sends a signed server callback
- 04Your server verifies, stores and acknowledges the event
Server-side credentialsSigned callbacksIdempotent processingTest before activation
Integration paths
Match control to your implementation.
Hosted checkout and payment links are the recommended launch paths. More direct integrations are enabled when the merchant's use case, security posture and provider arrangement require them.
02LINK
Payment links
Create and share payment requests for invoices and remote sales.
No-code collection03FIELDS
Hosted fields
Embed controlled payment fields within a branded checkout experience.
Provider eligibility applies04S2S
Server-to-server
Maximum server-side control for approved, PCI-compliant merchants.
Security review required05APM
Alternative methods
Connect eligible mobile money, wallets and bank-based methods.
Market-specific activation06SDK
Plugins and SDKs
Use configured ecommerce plugins and mobile integration paths where enabled.
Configuration dependentFive-step Quickstart
From credentials to a verified event.
- 01Receive the sandbox pack
Get test credentials, configured methods, return URLs and a signing secret for your approved environment.
- 02Create the payment server-side
Build the signed request on your server. Never expose merchant credentials or signing material in the browser.
- 03Send the customer to checkout
Use the returned redirect URL for hosted checkout, or present the payment link supplied for the transaction.
- 04Verify the callback
Validate the signature, process retries idempotently, store the event and return a prompt successful acknowledgement.
- 05Retrieve authoritative state
Use the server-side transaction state for fulfilment and reconciliation instead of relying on the customer's browser redirect.
Protocol contractIllustrative
SERVER → POST {CHECKOUT_URL}/api/v1/session
signed payment request
PLATFORM → { redirect_url }
BROWSER → redirect_url
customer completes payment
PLATFORM → signed server callback
SERVER → verify signature
deduplicate event
persist state
return HTTP 200Exact endpoints, required fields, signature rules and production URLs are supplied in the approved merchant environment.
Lifecycle and operations
Build for asynchronous payments.
Customer redirects improve experience; signed server events and state retrieval protect fulfilment, reconciliation and retry handling.
01Created
02Customer action
03Pending
04Approved or declined
05Captured
06Refunded or voided
Verify before acting.
- Use HTTPS endpoints
- Validate the supplied signature
- Deduplicate repeated events
- Return a prompt successful response
- Reconcile against server-side state
Manage the payment lifecycle.
- Status retrieval
- Capture where enabled
- Full or partial refund
- Void or reversal where supported
- Recurring workflows where approved
Activate only what is approved.
- Complete business onboarding
- Pass required test cases
- Confirm live routes and currencies
- Rotate to production credentials
- Monitor initial live transactions
Already discussing an integration? Contact developers@senropay.com and include your company and reference.