Customer reference
Xenos
Xenos posts Rabobank transactions from all its stores to the general ledger in AFAS.
Rabobank in your business workflow
Connect Rabobank to your ERP, online store and customer records. Use APPSS to build payment and verification workflows with your own rules for access, data and decisions.
Your business
Customer portal, CRM, store and ERP
APPSS
Workflow, permissions and data rules
Rabobank
Payments, account data and identity
Server of systems
Your ERP, store and customer records each have their own role. APPSS connects them to the Rabobank function that fits the step.
Payment requests and reconciliation
- Invoicing / ERP
- APPSS
- Payment Request API
Read the amount and reference from the open invoice. Let the authorised step create the payment link, then match the status retrieved from Rabobank to the invoice. Business Account Insight and Account Notification Service can support reconciliation where included in your setup.
Process an online store payment
- Online store
- APPSS
- Rabo Smart Pay
Link checkout to the original order. Check its status with Rabo Smart Pay and release fulfilment under your own rules. Route expired payments, discrepancies and refund requests to the right work queue.
Verify a customer’s identity
- Your own KYC portal
- APPSS
- Rabo Identity Services
Connect the customer case to an identity check, such as itsme through Rabo Identity Services. Record the verification outcome against the case. Use a separate IBAN name check where the workflow needs account validation.
Xenos
Rules of engagement
Your business rules define which systems, data and API operations each task may use. The server checks those rules before an action goes ahead.
Trust by design
Security
List the API operations allowed for each role. In this workflow, the agent can read payment status. A separately authorised role handles payment initiation, direct debits and refunds under your approval rules.
Data governance
Define the purpose, source, permitted fields, access and retention. For identity verification, an agent may receive only the relevant status and case reference. Keep identity documents and bank data at the designated source.
Decisions and audit trail
The server checks the role, case status and business rule before carrying out an action. Record who did what, using which source and when. Route incomplete or conflicting outcomes to an authorised reviewer.
Server of services
From verification to payment status, your business decides which steps customers handle, which agents carry out and when a person reviews the outcome.
Your own KYC portal
Give customers one place to complete verification and see their progress. APPSS controls the next step and who is allowed to handle it.
Step 1
Customer starts the check
The customer opens your company portal. The workflow starts a permitted check and links the return to the right case.
Step 2
Agent processes the status
The agent checks whether the required outcome has arrived and queues a reminder or a review under the case rules.
Step 3
Staff make the decision
An authorised member of staff reviews the outcome and decides whether to accept the customer. The portal shows the status the customer is allowed to see.
Payment request from invoicing
A staff member or an approved workflow step requests a link for the selected invoice. The workflow tracks payment status.
Payment status for customer service
An agent answers status questions from the provider’s confirmed status and hands discrepancies to finance.
Ravi and Sam at work
Two AI roles show how they handle bank status and follow the access rules in this example.
API documentation
Find the official sources from the integration library. Available functions depend on your product, setup and permissions.
Product access and authentication vary by API. PSD2 requires the account holder’s consent and access for an eligible party. Rabobank says iDIN ends on 31 December 2027 and will be replaced by itsme.
Loading integration details…