PMO Interface
Tx Authorization
Tx authorization
Our backend will consume this service by performing a
POST request to:
[Base-URL]/TxAuthorization.
Expected behavior:
Authorization request to process a funds transaction between two parties (Sender and Recipient). The partner will internally validate the balance, limits, and compliance rules (e.g., AML, Velocity), responding whether the operation is Authorized (accompanied by a TrackingIdentifier) or denied for a specific reason in NonAuthorizedReason.Body
application/json
Personal information. At least one of PhoneNumber or Email must be provided.
Personal information. At least one of PhoneNumber or Email must be provided.
3 chars
Response
200 - application/json
Ok
Null or empty if is not found. If Null or empty, Authorized will be ignored.
Max 10, Only these chars -> [-_a-zA-Z0-9.
If Null or empty, it will be Parner Prefix (configured in backend) + last four Account numbers (e.g. PRTN-0141).
Available options:
None, AccountBlocked, AccountBlockedByLaw, AccountBlockedByGovernment, ByVelocity, ByAmountLimit, ByAccumulateAmountLimit, InvalidAccount, InvalidParameter, InvalidCurrency, InvalidSenderData, InvalidDestinationData, InvalidExchangeRate, NonMatchingCurrencyAccount, InvalidAmount