Verified use case
What happened?
SAP's Taulia describes PayPal paying EY from its core ERP using PYUSD, with Coinbase as the recipient's custodian. The example shows how a stablecoin payment can start in accounts payable rather than a standalone wallet.
Context before technology
Background
The important starting point for a supplier payment is an approved liability. Changing the settlement rail does not remove the need to identify the supplier, verify approved payment details and close the invoice in the accounting system.
Taulia identifies a real PayPal-to-EY payment using PYUSD, with Coinbase as the payee's custodian. SAP's product documentation separately describes the Digital Currency Hub as connecting an ERP payment process to a blockchain-based rail. The documented example establishes the parties and broad workflow; it does not expose the transaction's accounting records.
Roles and records
How does the operating model work?
Initiate payment from the finance system
The company case describes PayPal paying from its core ERP. In a similar deployment, preserve the approved invoice and payment-run identity through any external hand-off; do not create a second, manual authorization record that finance cannot follow.
Send the designated settlement asset
The reported payment asset was PYUSD. Buyers should verify how an approved instruction identifies the token, network and destination, and where the rules for funding and any fees are applied. Those settings are not established for the reported payment.
Receive to the payee's custodian
Taulia names Coinbase for the recipient custody role. Custody identifies one participant in the workflow; it does not establish how, or whether, EY converted or withdrew the funds.
Close the invoice against independent evidence
A pilot should match the approved payable, the rail's status and the recipient's receipt. Handle mismatches as exceptions before an operator retries a payment. This is a buyer control, not a claim about PayPal's internal implementation.
Core infrastructure
- ERP payment instruction
- SAP Digital Currency Hub
- PYUSD
- Payee custody
Confirmed milestones
How did the use case develop?
- 01
2025
Taulia publishes the example
Taulia's payment guide identifies the parties, the ERP origin, the token and the payee custodian. This is the publication context, not an asserted payment date.
Evidence of adoption
What outcomes are publicly confirmed?
Named supplier-payment example reviewed
The public description is a documented example, not a count of payments across PayPal or EY.
Metrics are attributed to their reporting organization and date. They are not forecasts, endorsements or guarantees of equivalent results.
Current position
What are the latest confirmed updates?
- SAP's product documentation describes newer payment and statement-reporting options separately. Do not infer that those features were used in the PayPal example.
What buyers can learn
Why did this use case progress?
- Start with one supplier and one currency and preserve the usual sign-off and supplier validation.
- Before expanding, replay a rejected instruction and a confirmed transfer with a missing ERP status update. Verify that neither triggers a duplicate payment.
Limits of the evidence
- The sources do not establish the invoice amount, chain transaction identifier, fees, volume, or independently measured savings.
- The case does not establish that the recipient redeemed PYUSD or that the same workflow is available to every buyer.
Questions to take into procurement
- Can an accountant match the external payment to the original payable?
- Who confirms the payee wallet and network?
- How is a failed or late payment handled without paying the invoice twice?
Relevant FluidRWA directories
Common questions
Did the supplier have to be paid from a manual wallet?
Taulia describes the payment as originating from PayPal's core ERP through the SAP Digital Currency Hub.
Does this prove lower costs than a wire?
No. The cited sources do not provide comparable transaction pricing, operating cost, failure rates or settlement-time measurements for this payment.
Research record
FluidRWA reviewed the following public records. Company names are presented as plain text and are not outbound promotional links.
- SAP Taulia, Next-Gen Payments case example: https://taulia.com/wp-content/uploads/2025/06/replaced_Next-Gen-Payments_v3.pdf
- SAP Help Portal, Digital Currency Hub: https://help.sap.com/doc/d38a485b480f45849e0cf6ce8d80f65b/SHIP/en-US/732a7a3bd7c540b5a1b750f80ca29168.pdf
- SAP Help Portal, Digital Currency Hub release notes: https://help.sap.com/docs/SAP_DIGITAL_CURRENCY_HUB/4cf1ea7532b148bd82c3c7c75da21c0d?locale=en-US
Independent research summary, not legal, investment or regulatory advice. Public statements may be updated after the research cut-off.
Last updated
Questions about your project? contact@fluidrwa.com