XtalkPay
Payments within Xtalk.
Linked to commitments when it matters.
XtalkPay is the payment interface inside Xtalk. Payments remain optional and can be used independently of commitments.
Overview
XtalkPay operates as an interface and record layer. Payment execution, compliance, and settlement are handled by licensed third-party providers.
When a payment is linked to a commitment, it becomes proof that an agreed action has been completed — generating a verifiable Commitment Receipt.
Payment Flow
Example
A user agrees to make a payment. They complete it using card or crypto. The recipient receives fiat in their bank account. Xtalk records the outcome and, if applicable, marks the commitment as fulfilled with a verifiable receipt.
Payment Methods
All execution is handled by licensed partner providers. Xtalk does not process, settle, or hold funds.
Card Payments
Standard card payments via integrated licensed payment providers. PCI-DSS compliance managed by the processing partner.
Crypto → Fiat
Crypto payments converted automatically to fiat. The recipient receives local currency in their bank account. All conversion and custody handled by licensed partners.
Compliance Boundary
What Xtalk does not do
Does not hold customer funds — no float, no stored value
Does not custody digital assets — no crypto wallet or asset management
Does not perform settlement or clearing — handled by licensed partners
Does not operate as a payment processor — no acquiring, no issuing
All transactions executed directly between user and licensed providers
System Role
XtalkPay sits above payment rails as an interface and record layer.
Layer 1
Conversation
Where the commitment is made
Layer 2
Commitment
Optional agreed action
Layer 3
Payment
Executed by licensed provider
Layer 4
Proof
Immutable Commitment Receipt
Payments should remain frictionless.
Accountability should be optional, but available.