What this verification route checks
Verify.ET uses the submitted Dashen receipt details to start a traceable verification request. The result popup shows the request status, receipt details, and repeat confirmation signals after the first run.

Bank Verification Guide
Verify Dashen Bank transactions by submitting the receipt reference number through the bank-specific Verify.ET route. Ideal when finance or counter staff must log Dashen payment proof without juggling separate bank tools.
Dashen Bank receipt checks for teams that need a traceable transaction verification record.
Who this route is for
Businesses that accept Dashen transfers and need shared verification records across staff shifts.
Required Fields
Step-by-step
Need the SWIFT code instead? View Dashen SWIFT / BIC details.
Comparing tools? See Verify.ET vs manual checks, gateways, and open-source scripts.
Verify.ET uses the submitted Dashen receipt details to start a traceable verification request. The result popup shows the request status, receipt details, and repeat confirmation signals after the first run.
A successful Dashen check returns structured verification status plus available receipt fields such as amount, parties, reference, and timestamps when the provider data is available. Pending means the job is still processing; not found or failed means the details did not resolve to a usable receipt—re-check typing, suffixes, and provider status before releasing goods.
O/0 and I/1 swaps are common when reading printed receipts. Re-type carefully before marking a payment invalid.
Dashen references should not be submitted on CBE or BOA forms. Stay on the Dashen route for correct field handling.
Open the Dashen Bank verification page, enter the receipt reference number, and submit the request for a verification record.
Dashen verification uses the reference number from the transaction receipt.
Yes. Send the Dashen reference through the Verify.ET API with the correct bank field mapping described in the API docs.