API v1.31

October 15th, 2024

Implemented the cancellation endpoint to cancel OCT transfers that are held in Dodd-Frank.
Updated card onboarding logic to no longer check customer settings and instead use PAAI card data from Visa as the source of truth.
Enhanced errors shown to users when there are issues retrieving a quote.
Updated messaging if the transfer method is incorrect on POST Transfers.
Added Spanish and Dutch translations to GET /corridors endpoint.
Fixed POST Create Recipient to return translated values.

API v1.30

August 9th, 2024

Implemented functionality to support Visa Direct Bank Account and Mobile Wallet transactions.
- Bank Accounts or Account Funding Transfers from a debit card can be used to fund these transactions.
Implemented logic based on BIN performance provided by Visa to help decrease the likelihood of failed transfers due to unsupported cards in Original Credit Transaction programs.
Fixed small Spanish translation issues in Bank Transfer fields.
Adjusted numeric formats for Dutch-translated versions related to quote and transfer calculations.
Expanded Know Your Customer (KYC) logic to utilize a QR code that web UIs can take advantage of to provide more seamless guidance back to the mobile KYC experience.
Improved auditing of customer user events.
Updated the card acceptor value format to include both the sender and customer names for person-to-person transactions.
Updated an error message displayed for missing phone numbers.
Cleaned up translations on country names returned in the GET Countries endpoint.
Fixed label translations for required recipient account fields.
Improved error messaging for missing values on the POST Senders response.
Removed Sender information from the GET Transfer response that is not required for a receipt.
Updated customer reconciliation reporting to include FX Revenue

June 7th, 2024

Implemented AFT functionality that can be used to fund MasterCard Bank Account & Cash Pickup transactions.
Updated AFT transfers to ensure the expected transfer amount matches the quoted amount.
Added the ability to enable and disable the quote confirmation check when performing a transfer.
Added the ability to include MVV code in all OCT transfers.
Added the ability to see the response payload from RSPs to help determine whether transfers have succeeded or failed.
Resolved an issue where non-bank account transfers were not providing the correct decimal place.
Fixed an issue that was preventing OCTs from being submitted to Japan.

May 4th, 2024

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.

May 1st, 2024

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.

April 11th, 2024

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.

April 1st, 2024

Improved card onboarding process to stop the onboarding of unsupported cards that fail when posting transfers.

March 21st, 2024

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.

March 4th, 2024

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.

March 4th, 2024

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.