RBC Pay
Start Transaction
Select Location
Home / Developer

RBCPAY FOR DEVELOPERS

Build protected marketplace
transactions into your platform

Use Rbcpay APIs, webhooks and developer tools to create transactions, record agreed terms, track delivery and inspection, receive status updates and support buyer approval before funds release.
Get API access
View API documentation

REST API

Sandbox environment

Secure webhooks

Developer support

Start integrating in four steps

1

Create a developer account

Register your organisation and request API credentials.

2

Build in the sandbox

Test transaction flows without affecting live transactions.

3

Connect webhooks

Receive signed event notifications as transaction status changes.

4

Complete review and launch

Verify security settings, production access and operational readiness.

Everything you need to build

Transaction API

Create, retrieve and update transaction records.

Participant management

Connect buyers, sellers and authorised representatives.

Terms and milestones

Define price, currency, inspection and release conditions.

Delivery and tracking

Submit carrier, tracking and delivery evidence.

Disputes and evidence

Record disputes, documents and supporting information.

Reporting and reconciliation

Retrieve status, fees, activity and transaction references.

Transaction lifecycle

Draft

Terms agreed

Funds submitted

Seller delivered

Inspection

Buyer approved

Funds released

Your integration can display each status while Rbcpay maintains the authoritative transaction record.

Built for reliable integrations

Clear, structured API resources

  • Consistent resource identifiers
  • Idempotency for safe retries
  • Pagination and filtering
  • ISO 8601 timestamps
  • Detailed validation errors
  • Versioned API endpoints

Authentication and environments

Sandbox

Safe development and simulated lifecycle events.

Production

Live credentials issued after review.

API authentication

Server-side bearer credentials, scoped access and key rotation.

⚠  Never expose secret API credentials in browser or mobile client code.

Webhook events

●  transaction.created●  terms.accepted●  funds.submitted●  delivery.updated●  inspection.started●  dispute.opened●  buyer.approved●  funds.released

Verify every event

  • Validate webhook signatures
  • Use HTTPS
  • Reject stale timestamps
  • Return a 2xx response
  • Process events idempotently
  • Monitor failed deliveries

Security from the first request

TLS encryption

Scoped credentials

Signature verification

Audit records

Role-based access

Fraud monitoring

Rbcpay integrations must preserve transaction integrity, participant authorisation and the documented approval record.

Testing and go-live checklist

Before production

  • Complete sandbox scenarios
  • Test declined and disputed flows
  • Verify webhook retries
  • Restrict credential access
  • Configure logs and alerts

Launch readiness

  • Confirm legal business details
  • Review permitted use cases
  • Validate customer disclosures
  • Establish support contacts
  • Monitor initial production traffic

Errors, retries and support

Actionable errors

HTTP status, error code, message and field details.

Safe retries

Exponential backoff and idempotency keys.

Developer support

Integration questions, production incidents and webhook troubleshooting.

Developer resources

API guide

Read guide

API reference

Explore endpoints

Quickstart

Start building

Webhook guide

Configure events

Security guide

Review controls

Changelog

View updates

Frequently asked questions

Register your organisation and contact us with details of your platform and the transactions you intend to run through it. Sandbox credentials are issued first so you can build and test, and live credentials follow a review of your integration and your intended use.
The sandbox runs complete transaction flows end to end, including funding, delivery, inspection, approval, release, declines and disputes, with simulated lifecycle events and no real money moving at any point.
Every delivery is signed. Validate the signature before you trust the payload, accept deliveries only over HTTPS, reject stale timestamps, return a 2xx response promptly and process events idempotently so a retry cannot double-apply.
Release follows the release condition recorded on the transaction. When that condition is buyer approval, the buyer’s approval inside the inspection period moves the transaction to funds released, and your integration receives the matching webhook event.
Retry with exponential backoff and send an idempotency key on any request that creates or changes state, so a repeated call is applied once. Handle the error code rather than matching on the message text, since wording can change.
The agreed terms, the participants, price and currency, inspection and release conditions, carrier and tracking evidence, messages, uploaded documents and the full activity history. That record is what Rbcpay refers to if anything is disputed.

Build with Rbcpay

Connect your platform to a protected payment process designed for documented, high-value marketplace transactions.
Get API access
View documentation
API access, features and production availability depend on account approval, jurisdiction and permitted transaction type.