How We Integrate Into Your Ecosystem

Drive Ninja integrates with your bank's identity provider so customers never need a separate login. When embedded in your mobile app or web portal, the session token is passed seamlessly — users are authenticated the moment they arrive.

• Full OAuth 2.0 (RFC 6749) and JWT (RFC 7519) support
• One time token provided via URL parameter, cookie, or header when embedded in webview/iframe and exchanged by the web client for valid session token
• Token refresh and server-side verification supported
• No separate registration step — valid bank customers have instant access
• Alternative token-based systems supported on a case-by-case basis

Drive Ninja fully supports payment through fund transfer using the bank's native account transfer components. In order to present customer accounts, an API must be exposed detailing the account name, appropriate identifiers, and available balance. In addition, APIs are required to initiate and collect payment as required in the checkout journey. We have full flexibility on how this is achieved, as it varies based on the bank's desired processes and the chosen checkout journey.

• Full support for account-to-account fund transfers using bank's native components
• API integration to retrieve customer accounts — name, identifiers, and available balance
• APIs to initiate and collect payment at appropriate points in the checkout journey
• Fully flexible implementation — adapts to the bank's processes and checkout flow
• Seamlessly combined with other payment methods in mixed-payment checkout

For real-time insurance pricing embedded into the application, we require an API which accepts vehicle details and customer ID and returns a real-time price. We can also integrate based on customer profile to provide indicative pricing, or use static pricing based on industry averages. In all cases we can integrate directly with takaful journeys to get a full quote. For non-bank customers (or as required for existing customers) we can collect additional required information in order to provide real-time or indicative pricing as part of the vehicle display.

• Uses API integration for real-time quotation alongside vehicle pricing
• Built-in flows to gather additional customer data if required
• Quote activation via API or redirect-based flow at any time in the research or purchase phase
• Multiple quotes from multiple vendors fully supported

Drive Ninja can fully integrate into one or more loyalty schemes, allowing customers to spend and accrue points as part of their vehicle purchase. For spending points, we need endpoints to retrieve the points balance and monetary value (with any constraints such as min/max spend), authorise the spend, and finalise the spend. Redirect-style flows are also supported. For accruing points, we need an API that shows which points can be earned and, given details of the payment — cash, points, and financial products selected — returns the balance that will be accrued.

• Full integration with one or more loyalty schemes for spending and accruing points
• Endpoint to retrieve points balance, monetary value, and constraints (min/max spend)
• Endpoints to authorise and finalise point spend on vehicle purchases
• Redirect-style flows supported as an alternative to direct API integration
• Accrual API: returns points earned based on payment mix (cash, points, finance products)

The solution incorporates strong cryptographic controls to protect data throughout its lifecycle. All data in transit is encrypted using TLS 1.2 or higher, and sensitive data at rest is encrypted where applicable. Secure key management, data integrity controls, and non-repudiation mechanisms are built in. Sensitive data classification controls are supported, and data processing environments can be segregated in accordance with client policy. The platform does not store card payment data — payment flows utilise secure third-party hosted checkout mechanisms to minimise PCI exposure.

• Encryption of data in transit (TLS 1.2+) and sensitive data at rest
• Secure key management practices and data integrity controls
• Non-repudiation mechanisms and secure communication protocols
• Sensitive data classification with environment segregation per client policy
• No card payment data stored — secure third-party hosted checkout minimises PCI exposure