- The alias exists
- The associated customer is currently active
- The customer’s metadata is accessible (e.g. whether they are an individual or a business)
When to Use It
- Push Payments: Before a user sends money, verify the recipient’s alias.
- Pull Payments: Before requesting payment from a customer, confirm that their alias is active and valid.
- Risk & UX Decisions: Retrieve additional metadata (like whether the customer is a business) and tailor your flow accordingly.
- Avoid Preventable Failures: Prevent unnecessary calls to the Payments API that would otherwise fail due to inactive or non-existent aliases.
Resolve a Customer
Resolve customer
response
{payment_address}
with the alias you wish to resolve (e.g. ziyadparekh@safepay
).
By resolving an alias before attempting a payment, you not only improve reliability but also enhance confidence and security for your users. This API acts as the first touchpoint for validating intent and building trust into your payment flow.