What this verification route checks
Verify.ET uses the submitted Awash 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 Awash Bank transactions by submitting the receipt URL or token from the Awash payment receipt. Link- or token-based inputs reduce retyping long opaque identifiers.
Awash Bank receipt URL and token verification for payment confirmation workflows.
Who this route is for
Teams receiving Awash digital receipts as links or tokens rather than short FT codes.
Required Fields
Step-by-step
Need the SWIFT code instead? View Awash SWIFT / BIC details.
Comparing tools? See Verify.ET vs manual checks, gateways, and open-source scripts.
Verify.ET uses the submitted Awash 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 Awash 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.
Chat apps sometimes split links. Paste the full URL or the token portion the form expects.
If the upstream receipt can no longer be resolved, ask for a fresh receipt export from the customer’s banking channel.
Open the Awash Bank route, enter the receipt URL or token, and submit it to create a Verify.ET verification request.
Yes. The Awash Bank route accepts the receipt URL or token used by the verification workflow.
Not on the public Awash route. Provide the receipt URL or token field shown on the form.