Start in Receive
Your account already has a public receiving address. Share its Bankeiz payment link in a message, on an invoice or wherever you can publish a link. Add an optional amount when you want to request a specific payment. Opening the link prepares the destination. The customer can use their balance, add money by card or choose Pay with a Note, then review and approve the payment in their own account.
Keep card checkout on your site
Choose Embedded checkout to copy the existing Receiz widget. Paste it into a custom HTML block that permits scripts. Customers enter an amount and complete the supported card checkout within the site. Receive also supplies your Receiz checkout link for places that cannot run a widget. The current widget lets the customer choose an amount; it does not inherit the optional amount in your Bankeiz request. Your Receiz profile must be public for this checkout.
Receive an original Note
Your Bankeiz payment button supports Reserve, Settlement and Settlement Reserve Notes through one Pay with a Note option. The payer deposits a valid Note they own, its credit reconciles through Receiz, and the ordinary account payment pays the merchant. The complete source chain and funding composition remain intact. This requires a confirmed deposit before spending; a copied image or a Note addressed to someone else cannot pay an order. Receiz’s separate embedded widget retains its legacy Wallet Note compatibility path.
Build into your application
Use the pinned Receiz SDK for a custom checkout, with the merchant, price and order reference selected by your trusted application. Reuse the existing checkout host and account operations instead of creating a second balance or payment ledger. The integration reference provides a typed example, exact response checks, recovery guidance and the boundaries of Notes, account payments and commerce capabilities.
Confirm before delivery
A button click, a checkout session, a browser message or a success URL is not payment confirmation. Check the original session with Receiz from your trusted application, match the intended merchant, exact amount and confirmed account credit, then record fulfillment once. Keep an interrupted session reference and inspect it before asking the customer to pay again.
One receiving account
Use the same identity for customer payments, your own payments and their connected history. A website integration changes where the customer starts; it does not create another account for the merchant. Card availability, limits and website permissions follow their existing host and processor rules. Keep the customer’s approval and the actual payment result explicit.
Method, sources and assessment
This explanation describes the supported implementation. Exact protocol requirements come from the pinned Receiz contracts and original sources. A reference result does not qualify a production deployment or a physical device.