Security at PayEast

Your money.
Your decision.

Trust starts with clear permissions, authenticated access and approval that remains with the customer.

Your application
Requests a payment
PayEast
You review and approve
You decide
Connected applications

A connection.
Not a blank cheque.

A supported application can request a payment. It cannot approve that payment for you.

Choose what to share, review each request, and disconnect an application when you need to.

Explore customer control
Trust, by design

Built around
permission.

01

Your approval

Each payment request comes back to the customer for a decision.

02

Your connection

Applications ask for defined permissions. Customers can revoke access.

03

Your clarity

Review the details. Follow the status. Keep the reference.

Security at PayEast
What that means for you

See it. Review it.
Decide.

Connected apps have defined access

Partner access uses OAuth and scopes. A connection grants the permissions you agreed to; it does not remove payment approval.

Approval remains inside PayEast

You review the request and choose to approve or decline. Never share your PayEast PIN, password or one-time codes with a merchant or connected app.

Connections can be revoked

The beta connected-app experience includes revocation. Developers should handle revoked connections and ask you to reconnect when appropriate.

Report an issue

For a security concern, contact legal-compliance@eylorin.com. Share a description and safe reproduction steps. Do not send credentials, PINs or identity documents.

Security features and live-service permissions are validated as releases progress. This page makes no certification, licence or uptime claim.