This solution provides you the capability to transfer funds from your provisioned Maya mother account to your recipients.
Transfer can have four (4) states: CREATED, APPROVED, DECLINED and CANCELLED. You can start by creating intents to transfer then execute after your validation.
Money Movement solution uses API keys to authenticate requests.
Your API keys carry many privileges. For a secure handover of API keys, they will be sent to your nominated recipient. These keys will be stored in a file that is encrypted using your public GPG keys. Be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.
Use your API key in the Authorization header for every call to Money Movement’s endpoints. Set it as the username on the Basic authentication process with a blank password.
- Initial values
- Replace the username with the API key and leaving the password blank
- Expected base64 encoding
You are required to send a Request-Reference-No in the HTTP header for each API request. This field will receive an alphanumeric string with a maximum of 50 characters.
UUID generator when creating your Request-Reference-No.We recommend to use a
Creating transfers always result in a new intent even when using the same request reference number. As long as a new
transferId is returned, it’s treated as a new independent transaction. We suggest you randomly generate a new request reference number for each transfer intent.
Money Movement does NOT check the existence of the request-reference-no being passed by the integrating system.
Each intent is assigned its own
transferId. This ID is always unique and will serve to facilitate idempotency during execution. Each transfer can only be executed exactly once regardless of the provided request reference number. The same applies for cancellation.
Currently, Money Movement does not support retries of the same transaction and all errors are final (i.e. temporary errors are not distinguishable).
Maya enforces rate limiting in its endpoints. We encourage you to implement some sort of exponential back-off behavior in their invocations to Maya endpoints upon receiving an
HTTP 429 response.
A report that is generated daily (every 4AM) and will be sent to your nominated MDTR recipient. This report captures all yesterday’s successful and failed transactions.
|Headline (row 1)||Headlines of the report including the Client ID||Partner Name MDTR Report|
|The date when report was generated. Date is in
|Column Name||Description||Sample Data|
|DateTime||Date/Time the transaction was performed in PHT.
|Target PAN||Target wallet account details. Value could be hash / masked if it is the PAN (Primary Account Number)||542482******5545|
|Target MSISDN||Mobile number linked to the target wallet account.||639123456789|
|Target type||Target account type. (default
|Partner RRN||Transaction Reference number you have provided.||fce48a15-7e54-4c36-b2af-eee19a6abd9c|
|MI3 RRN||Transaction ID generated by Money Movement.||595213fb-f040-438e-ba55-4dc2bd183de4|
|Amount||Transaction Amount in Philippine peso||100.00|
|Response Code||Transaction response||0 (Please see list of Error Codes)|
|Total Debit Amount||Total amount debited to your wallet account||1900.00|
|Total No. of Successful Transactions||Total count of successful transactions on the generated report||8|
|Total No. of Failed Transactions||Total count of failed transactions on the generated report||3|
|Current balance as of generation date||This is your account’s remaining balance by the time this report was generated.||55.00|
|Available balance as of generation date||This is your account’s remaining balance by the time this report was generated.||55.00|
Get your end-of-day (EOD) account balance given your specific date by reaching out to your Relationship Manager to request for extraction.