ReadyRemit v1.28 2024-05-06
14 days ago by Brian West
- Added a validation endpoint to check the creation status of a transfer in the event the POST transfer request times out.
- This endpoint accepts the quote ID submitted in the transfer request and confirms if the transfer was completed or failed to process.
- Added functionality to log the acceptance of published privacy policies and terms and conditions.
- Updated the quoting by receive amount process to include Visa bank account/wallet as a transfer type.
- Added support for card brand Maestro in ReadyRemit.
- Fixed the release of to-account transfers from a Dodd-Frank hold.
- Fixed a GET quote rounding error if the currency specifies zero decimal places.
- Updated text in the ReadyRemit API to return a clearer message, corrected capitalization and improved the translation text for Spanish.
- Fixed the GET quote endpoint to account for minimum limits for USA transfers.
- Fixed the sort order of fields returned on the GET Transfer endpoint.
- Fixed multiple endpoint responses so account fields show a name instead of an ID.
- Fixed logic to ensure a card is blocked if a bank does not accept OCT transfers.
ReadyRemit v1.27.3 2024-04-29
18 days ago by Antranik Andreh Kiloyan
- Changed the character limit for "Address ZIP" field for person & business senders to minimum: 2 & maximum: 10.
- Introduced new logic to make "Phone Number" field for person & business senders optional by customer.
- Introduced a new optional field for person senders called "Address State Province" that can be utilized for senders with international addresses.
ReadyRemit v1.27.2 2024-04-10
about 1 month ago by Antranik Andreh Kiloyan
- Introduced new "Purpose of Payment" dropdown field for Push to Card transfers to specific corridors.
- "Purpose of Payment" is mandatory for the following corridors: Argentina, Chile, Colombia, Egypt, India, & Mexico.
ReadyRemit v1.27.1 2024-03-27
about 2 months ago by Antranik Andreh Kiloyan
- Improved card onboarding process to stop the onboarding of unsupported cards that fail when posting transfers.
ReadyRemit v1.27 2024-03-21
about 2 months ago by Brian West
- Fixed issue related to duplicated bank accounts in the GET/Banks endpoint.
- Introduced new logic to support quoting by receive amount for Mastercard Bank Account & Cash Pick-Up transfers.
- Fixed issue with rounding FX Rates in the GET/Transfer endpoint.
- Fixed issue with the create card flow only to allow one card per session.
- Fixed translated labels on card creation screens to be user-friendly and resolve consistent capitalization.
- Fixed discrepancies in the SLA information displayed to users on the confirmation response to the user.
- Removed a default source of funds value from transfers that do not require the value.
- Added support for email and webhook status reporting for Latitude.
- Added error handling support for RSP response codes.
- Improved the release flow for transfers that are placed on OFAC hold.
- Added validation into POST Sender to prevent a PO BOX address from being used.
- Improved the error messaging in multiple API responses to be more user-friendly.
- Fixed the daily settlement and reconciliation of canceled transfers that are reported.
ReadyRemit v1.26 2024-03-04-1
2 months ago by Brian West
- Enabled payer limits for Cash Pickup transfers for the following corridors.
- Peru, Mexico, Honduras, El Salvador, Colombia, Brazil
- Updates to the translation strings to ensure correct Spanish.
- Fixed the GET Recipient with Accounts endpoint to ensure more useful error messaging.
- Fixed the stored markup percentage to match what was presented to the user during a quote.
- Fixed the GET Transfers response to return a rounded FX rate.
- Updated the POST /senders endpoint to accept an 18-character ID number.
- Fixed a problem where some transfer limits were not being adhered to when more than one transfer was submitted in a day.
- Improvements to our reporting around daylight savings.
ReadyRemit v1.25 2024-02-20
2 months ago by Brian West
- Improved how card onboarding works for creating cards in ReadyRemit:
- Introduced new property when creating an onboarding session called “Entity Mode”.
- “Entity Mode” property allows customers to generate dynamic fields based on the entity type (Sender or Recipient).
- Introduced new layer of validation for card creation specifically for senders, to improve acceptance rates & decrease fraud.
- When using the POST/Create Card endpoint for sender cards, sender-ID is required either through the token or through the endpoint request body. When entity mode is sender & there is no sender-ID, card creation will fail.
ReadyRemit v1.24.5 2024-01-18
4 months ago by Brian West
- Updated ReadyRemit to support OCT transactions in addition to the existing transfer types. Users are now able to send funds directly to a recipient’s debit card.
ReadyRemit v1.24 2024-01-05
4 months ago by Brian West
- Added validation to Quote by Receive Amount transfers to abide by corridor transfer limits, allowing transfer request customers to create transfer requests using either a send or a receive amount. Talk to your Support Rep for details.
- Updated error messaging on the POST /senders endpoint to display a more user-friendly message if problems are encountered.
- Improvements to the OFAC and Dodd/Frank transfer hold and release process.
- Updated the Get Quote endpoint to return an exchange rate rounded to four decimal places.
- Ensured sender creation allows for cities that have hyphens in the name.
- Updated transfer requests so that if a transfer submission fails three times a status is returned to prevent more retries.
- Updated translated strings.
- Updated transfer requests to ensure the source currency has the correct ISO code for Quote by Receive amount transfers.
- Adjusted the GET Transfer endpoint to return the correct fee amount for Quote by Receive Amount transfers.
- Improvements to transfer status logging.
- Improvements to security measures for encrypting account numbers.
ReadyRemit v1.23 2023-11-28
6 months ago by Brian West
- Support for Visa Push to Account in India and Push to Wallet in the Philippines in B2C API use cases
- Account numbers returned in API responses are now encrypted.
- Missing Spanish translations have been added.
- Additional payer locations were added for Columbia, Guatemala, Honduras, and Brazil.
- Get Partner-Payers API updated to return an empty array if no payers exist.
- Improved logged error messaging when creating a transfer through the Post Transfer API.
- Added functionality to handle a user’s abandoned KYC requests more efficiently.
- Improved logged error messaging if SLS errors are encountered for easier debugging.
- Post Transfer API response body updated to match the value returned in the Get Transfer response body.
- Get Transfer API endpoint updated to return the field name instead of ID on transfer fields.
- Added field IDs to the response from the Get Quote API endpoint.
- Fixed an issue where an incorrect sender was attached to a transfer if the assigned sender did not have an RSP sender ID.
- Updated our report versions to fix inconsistencies in transfer settlement and reconciliation.