Previous updates

Date Change
Jan 15, 2020 Decrease in webhook timeout period to 10 seconds

Jan 15, 2020 - Decrease in webhook timeout period to 10 seconds

What is changing?

The webhook timeout period will be decreased to 10 seconds from 20 seconds.

How does it affect you?

PEX will retry webhook calls if we fail to receive a response from your server within the timeout period. Instead of waiting 20 seconds for a response, we will now wait for 10 seconds before initiating a series of retry calls. The retry calls will continue to be sent at 15, 30, 60 and 120 seconds later, and one final retry attempt will be made 3600 seconds (1 hour) later. This will allow us to speed up retry calls in the case of network outages or other failures.

Date Change
May 29, 2019 Planned deprecation of POST /Business/OneTimeTransfer
Planned deprecation of DELETE /Business/OneTimeTransfer{Id}
Introducion of a new endpoint for tracking remaining spend for time-based spend limits

May 29, 2019 - Planned deprecation of endpoints relating to one time transfers and a new endpoint

What is changing?

1.

Due to a lack of active use, PEX is deprecating

  • POST /Business/OneTimeTransfer
  • DELETE /Business/OneTimeTransfer{Id}

How does it affect you?

These end points will no longer be operational after May 29 2019. Transfers to and from the PEX business account should be done via the PEX Admin web app at https://admin.pexcard.com

2.
PEX is proposing a new endpoint to help you track the dollar amount spent against a cardholder or category time-based spend limit. More details on time-based spend limits can be found here. Please see the proposed request/response structure below. Comments and feedback are welcome:

GET /Details/AccountDetails/{Id}/RemainingLimit
{
CardId:1232,
GlobalLimit:
[
   {
Type: “Annual”,
Limit: 4000.00,
Remaining: 345.20
   }
],
CategoryLimit:
[
   {
Type:“Annual”,
Category:“Train Travel”,
Limit: 2000.00,
Remaining: 2000.00
   },
   {
Type:“Annual”,
Category:“Air Travel”,
Limit: 2000.00,
Remaining: 120.50
   }
]
}
How does it affect you?

With the new endpoint GET /Details/AccountDetails/{Id}/RemainingLimit you will be able to retrieve data on cardholder spend torwards a pre-assigned spend limit.

When are these changes happening?

PEX is planning to release this change on May 29, 2019.

Date Change
April 24, 2019 Planned deprecation of POST /Business/Admin endpoint

April 24, 2019 - Planned deprecation of POST /Business/Admin

What is changing?

Due to a lack of active use, PEX is deprecating POST /Business/Admin endpoint on April 24th 2019. This end point will no longer be operational after 24th April 2019.

How does it affect you?

After this endpoint is deprecated, you will not be able to create new administrators via POST /Business/Admin end point. The preferred way to create administrators is through the PEX Admin web interface at http://admin.pexcard.com. If you were planning to use this endpoint in the future, please let us know as soon as possible.

When is this change happening?

PEX will release this change on April 24 2019.


Date Change
March 1, 2019 Adding four new properties to "Card Status Change" webhook

March 1, 2019 - "Card Status Change" Webhook

What is changing?

PEX is adding four new properties in "Card Status Change" Webhook

  • CardOrderId : Order ID returned as a response to POST/Card/CreateAsync, when you submit card creation request.
  • FirstName : First Name of the card holder
  • LastName : Last Name of the card holder
  • CustomId : User defined Id which can be assigned to Card holder profile

Proposed changes in "Card Status Change" webhook

{
"CallbackTime": "2016-08-22T12:20:53.7335395+03:00",
"Data": {
"AcctId": 123213234,
"TransactionType": "CARD",
"Description": "Status Change",
"FirstName": "Jane",
"LastName": "Doe":
"CustomId": "F1Q52343SF",
"CardList":[
{
"CardId": 6231,
"IssueDate": "2014-11-26T00:00:00",
"ExpirationDate": "2017-11-30T00:00:00",
"Last4CardNumber": "1212",
"CardStatus": "CLOSED",
"CardOrderId": 55233
}
]
}
}
How does it affect you?

These new fields enable you to match a card order to a set of cards using the Card Status webhook

When is this change happening?

PEX will release this change on March 1, 2019.

Date Change
Wednesday, May 30, 2018 Adding a TransactionTypeCategory and MetadataApprovalStatus properties to endpoints returning transactions details

Wednesday, May 30, 2018 - API

What is changing?

PEX is adding two new properties as part of response in GET/Details/TransactionDetails, GET/Details/TransactionDetails/{Id} and GET/Details/AllCardholderTransactions

  • TransactionTypeCategory :- This gives more information about TransactionType. For TransactionType = Transfer there could be multiple TransactionTypeCatagory such as Business account fee or Card account fee etc

  • MetadataApprovalStatus :- Specifies the the status of the metadata (Tags, receipt image file) associated with transaction. Possible values are Approved, Rejected, Ignored and Not Reviewed.

How does it affect you?

These properties provide ability to filter transaction retrieval on basis of approval status and transaction type category. This is backward compatible change. You may choose to ignore new properties

When is this change happening?

PEX will release this change on May 30, 2018.

Date Change
Wednesday, May 2, 2018 Adding a MerchantRequestedAmount property to endpoints returning network transactions details
Thursday, April 26, 2018 Adding a Name property in Tags[] array to endpoints returning transaction details

Wednesday, May 2, 2018 - API & Webhooks

What is changing?

PEX is adding a new property MerchantRequestedAmount. This field will indicate the amount merchant requested to complete the transaction. In most cases TransactionAmount and MerchantRequestedAmount will have same amount value except few scenarios like partial authorization This new property will be added in Our Webhook calls and below API end points

  • GET /Details/{Id}/NetworkTransactions
  • GET /Details/NetworkTransactions

How does it affect you?

If you want to monitor Partial Authorization transaction on your PEX card, you can start consuming new property in API end points and webhooks, else you can choose to ignore it. This is backward compatible change.

When is this change happening?

PEX will release this change on May 2, 2018.

Thursday, April 26, 2018 - API

What is changing?

PEX is adding a new property Name in Tags[] array. Currently only Tag Value is exposed in the endpoints, Name will be added as part of this change, so that it would make more sense along with value. This new property will be added in below three end points

  • GET /Details/AllCardholderTransactions
  • GET /Details/TransactionDetails
  • GET /Details/TransactionDetails/{Id}

How does it affect you?

If you are accessing transaction tags via API endpoints, the new Name property will help you to identify the name of the tag. You may choose to ignore this new property if you do not consume tag information via API endpoints. Note that tags are not available for all customers.

When is this change happening?

PEX will release this change on April 26, 2018.

Date Change
Wednesday, February 28, 2018 New API endpoint for retrieving Network Transaction details
Introducing Spend controls per time period (per week, month, year or over lifetime)
Wednesday, March 21, 2018 Introducing new CustomId field for Card holder profile API end points.
Wednesday, March 28, 2018 Planned depreciation of V1 webhooks

Wednesday, February 28, 2018 - API

What is changing?

PEX is releasing two new API endpoints.

  • GET /Details/{Id}/NetworkTransactions: Gives details about network transactions for specified card account for a given duration
  • GET /Details/NetworkTransactions: Gives details about network transactions for a business for a given duration

You can get details about Authorization, Settlement, Decline, Reversal, and PIN transactions via the above endpoints. Card funding transactions will NOT be included as part of the response. For more information, please refer to the API documentation here

How does it affect you?

You can take advantage of these two endpoints to get more detailed information about your PEX transactions.

When is this change happening?

We will release this change on February 28, 2018.

What is changing?

You can now set spend limits for a given time period (daily, weekly, monthly , yearly, or over the lifetime of the card) through the API. Also you can retrieve information about existing time-based spend limits if already set. Below are the endpoints affected by this change.

  • GET /Card/SpendRules/{Id}/Advanced
  • PUT /Card/SpendRules/{Id}/Advanced
  • GET /Details/AccountDetails/{Id}/Advanced
  • GET /SpendingRuleset/{Id}/Advanced
  • GET /SpendingRuleset/{Id}/Advanced/Cards
  • GET /SpendingRuleset/Advanced
  • POST /SpendingRuleset/Advanced
  • PUT /SpendingRuleset/Advanced

For more information, please refer to the API documentation here

How does it affect you?

You will notice 4 new properties (WeeklySpendLimit, MonthlySpendLimit, YearlySpendLimit, LifetimeSpendLimit) in the above endpoints. If you are not using these new spend rules, you can ignore the new fields.

When is this change happening?

We will release this change on February 28, 2018.

Wednesday, March 21, 2018 - API

What is changing?

PEX is introducing new field in API endpoints related to cardholder profile. CustomId field is an user-defined, optional field, up to 50 characters long.

Below is the list of end points affected by this change

  • GET /Details/AccountDetails/{Id}
  • GET /Details/AccountDetails/{Id}/Advanced
  • GET /Details/AccountDetails
  • GET /Card/CardOrder/{Id}
  • GET /Card/Profile/{Id}
  • GET /SpendingRuleset/{Id}/Advanced/Cards
  • GET /SpendingRuleset/{Id}/Cards
  • GET /Group/{id}
  • PUT /Card/Profile/{Id}
  • POST /Card/CreateSync

How does it affect you?

CustomId is an user-defined optional field. You can use it to tag each cardholder with an Id which you can refer back to or you can ignore it if you do not want to utilize it. This is a backword compatible change.

When is this change happening?

We will release this change on March 21, 2018.

Wednesday, March 28, 2018 - Webhooks

What is changing?

V1 webhooks are being depreciated. You will no longer receive any calls on your V1 endpoints. If you wish to receive webhook notifications, please contact API support to receive V2 notifications.

How does it affect you?

If you wish to continue using Webhook notification, please plan on switching to V2 version.

When is this change happening?

We will release this change on March 28, 2018.

 
Date Change
Wednesday, February 28, 2018 Production: Planned depreciation support to protocol TLS 1.0
New API endpoint for retrieving Network Transaction details
Introducing Spend controls per time period (per week, month, year or over lifetime)
Wednesday, March 28, 2018 Planned depreciation of V1 webhooks

Wednesday, February 28, 2018 - API

What is changing?

Pex is ending support for TLS 1.0 and will only support TLS 1.1, 1.2.

How does it affect you?

If you are using an old operating system or library to connect to Pex, it is possible that your connection will fail.
Check your code and custom applications to ensure that they are able to utilize TLS 1.1 or TLS 1.2.
More information can be found here

When is this change happening?

We will release this change in Sandbox on January 31st 2018 and in production on February 28, 2018.

What is changing?

PEX is releasing two new API endpoints.

  • GET /Details/{Id}/NetworkTransactions: Gives details about network transactions for specified card account for a given duration
  • GET /Details/NetworkTransactions: Gives details about network transactions for a business for a given duration

You can get details about Authorization, Settlement, Decline, Reversal, and PIN transactions via the above endpoints. Card funding transactions will NOT be included as part of the response. For more information, please refer to the API documentation here

How does it affect you?

You can take advantage of these two endpoints to get more detailed information about your PEX transactions.

When is this change happening?

We will release this change on February 28, 2018.

What is changing?

You can now set spend limits for a given time period (daily, weekly, monthly , yearly, or over the lifetime of the card) through the API. Also you can retrieve information about existing time-based spend limits if already set. Below are the endpoints affected by this change.

  • GET /Card/SpendRules/{Id}/Advanced
  • PUT /Card/SpendRules/{Id}/Advanced
  • GET /Details/AccountDetails/{Id}/Advanced
  • GET /SpendingRuleset/{Id}/Advanced
  • GET /SpendingRuleset/{Id}/Advanced/Cards
  • GET /SpendingRuleset/Advanced
  • POST /SpendingRuleset/Advanced
  • PUT /SpendingRuleset/Advanced

For more information, please refer to the API documentation here

How does it affect you?

You will notice 4 new properties (WeeklySpendLimit, MonthlySpendLimit, YearlySpendLimit, LifetimeSpendLimit) in the above endpoints. If you are not using these new spend rules, you can ignore the new fields.

When is this change happening?

We will release this change on February 28, 2018.

Wednesday, March 28, 2018 - Webhooks

What is changing?

V1 webhooks are being depreciated. You will no longer receive any calls on your V1 endpoints. If you wish to receive webhook notifications, please contact API support to receive V2 notifications.

How does it affect you?

If you wish to continue using Webhook notification, please plan on switching to V2 version.

When is this change happening?

We will release this change on March 28, 2018.

 
Date Change
Wednesday, January 31, 2018 SandBox: Planned depreciation support to protocol TLS 1.0
Wednesday, February 28, 2018 Production: Planned depreciation support to protocol TLS 1.0
Wednesday, March 28, 2018 Planned depreciation of V1 webhooks

Wednesday, January 31, 2018 - API

What is changing?

We are terminating the POST/Card/Create endpoint.
Currently PEX offers two separate end points to create cards POST Card/Create and POST/Card/CreateAsync.
POST/Card/CreateAsync will continue to exist for creating cards.

How does it affect you?

Please plan to use POST/Card/CreateAsync going forward if you are using POST/Card/Create.
POST/Card/Create creates a card order with a single card per request and POST/Card/CreateAsync can be used for creating a card order with single or multiple cards per request. Both the end point have same request structure.

When this change is happening?

We will release this change on January 31, 2018.

Wednesday, February 28, 2018 - API

What is changing?

Pex is ending support for TLS 1.0 and will support TLS 1.1, 1.2.

How does it affect you?

If you are using a very old operating system or library to connect to Pex, it is possible that your connection will fail.
check your code and custom applications to ensure that they are able to utilize TLS 1.1 or TLS 1.2.
More information can be found here

When this change is happening?

We will release this change in Sandbox on January 31st 2018 and in production on February 28, 2018.

Wednesday, March 28, 2018 - API

What is changing?

V1 webhooks are being depreciated. You will no longer receive any calls on your V1 endpoints. If you wish to receive webhook notifications, please contact API support to receive V2 notifications.

How does it affect you?

If you wish to continue using Webhook notification, please plan on switching to V2 version.

When this change is happening?

We will release this change on March 28, 2018.

 
Date Change
Wednesday, January 31, 2018 1. Planned depreciation of old sandbox URLs
2. Planned depreciation of the API end point POST /Card/Create
Wednesday, January 31, 2018 SandBox: Planned depreciation support to protocol TLS 1.0
Wednesday, February 28, 2018 Production: Planned depreciation support to protocol TLS 1.0
Wednesday, March 28, 2018 Planned depreciation of V1 webhooks

Wednesday, January 31, 2018 - API

What is changing?

We are depreciating the sandbox URLs and replacing them with the new URLs.
This change will affect only Sandbox environment and not any other environment.
Below is the comparison between old URLs and new URLs

OLD URLs NEW URLs
External APIs https://corebeta.pexcard.com/api/v4/ping https://sandbox-coreapi.pexcard.com/v4/ping
Admin web site https://corebeta.pexcard.com/apps/admin.html https://sandbox-admin.pexcard.com/admin.html
Card holder web site https://corebeta.pexcard.com/apps/cardholder.html https://sandbox-ch.pexcard.com/cardholder.html
How does it affect you? Plan on consuming new Sandbox URLs. When this change is happening?

We will release this change on January 31, 2018.

Wednesday, January 31, 2018 - API

What is changing?

We are terminating the POST/Card/Create endpoint.
Currently PEX offers two separate end points to create cards POST Card/Create and POST/Card/CreateAsync.
POST/Card/CreateAsync will continue to exist for creating cards.

How does it affect you?

Please plan to use POST/Card/CreateAsync going forward if you are using POST/Card/Create.
POST/Card/Create creates a card order with a single card per request and POST/Card/CreateAsync can be used for creating a card order with single or multiple cards per request. Both the end point have same request structure.

When this change is happening?

We will release this change on January 31, 2018.

Wednesday, February 28, 2018 - API

What is changing?

Pex is ending support for TLS 1.0 and will support TLS 1.1, 1.2.

How does it affect you?

If you are using a very old operating system or library to connect to Pex, it is possible that your connection will fail.
check your code and custom applications to ensure that they are able to utilize TLS 1.1 or TLS 1.2.
More information can be found here

When this change is happening?

We will release this change in Sandbox on January 31st 2018 and in production on February 28, 2018.

Wednesday, March 28, 2018 - API

What is changing?

V1 webhooks are being depreciated. You will no longer receive any calls on your V1 endpoints. If you wish to receive webhook notifications, please contact API support to receive V2 notifications.

How does it affect you?

If you wish to continue using Webhook notification, please plan on switching to V2 version.

When this change is happening?

We will release this change on March 28, 2018.

 
Date Change
Wednesday, December 27, 2017 Change to the signs used for transaction amounts in V2 webhooks
Wednesday, December 27, 2017 Addition of IsVirtual flag in API card endpoints
Wednesday, January 31, 2018 1. Planned depreciation of old sandbox URLs
2. Planned depreciation of the API end point POST /Card/Create
3. Planned depreciation of IP address whitelisting as a means to verify webhook origination
Wednesday, January 31, 2018 SandBox: Planned depreciation support to protocol TLS 1.0
Saturday, March 31, 2018 Planned depreciation of V1 webhooks

Wednesday, December 27, 2017 - Webhooks

What's Changing?

In order to represent the TransactionAmount consistently across the PEX platform, we are updating the sign (positive or negative) of the transaction value.

For example, the Settlement webhook currently shows "TransactionAmount": 10.00 which is the absolute amount debited from the account.

After the change, the Settlement webhook will show TransactionAmount with a negative sign. For example, "TransactionAmount" : -10.00
Only the V2 webhook will be affected by this change. The TransactionAmount signs will now be consistent with the signs used by transaction type in the associated API endpoints.

The table below summarizes the changes for TransactionAmount by type of webhook before and after the update.

Webhook Sign of TransactionAmount before update Sign of TransactionAmount after update
PIN Transaction Positive Negative
Settlement Positive Negative
Authorization Positive Negative
Decline Positive Negative
Reversal Negative Positive
Settlement of merchant credit (e.g. merchandise return) Negative Positive

How does it affect you?

If your system depends on the sign of the transaction amount sent in the PEX webhook, you may need to make changes.

When is this change happening?

All webhooks starting version 2.0.1.3 and later will use the signs documented in the table above. Customers will start receiving the new webhooks on December 27th 2017.

Wednesday, December 27, 2017 - API

What's Changing?

We are adding a new (boolean) property "IsVirtual" in endpoints related to card functionality. See below for the full list of affected endpoints.

GET /Card/Profile/{Id}
GET /Details/AccountDetails
GET /Details/AccountDetails/{Id}
GET /SpendingRuleset/{Id}/Cards
GET /Details/AccountDetails/{id}/Advance
GET /Group/{Id}
 How does it affect you?

The "IsVirtual" flag allows API users to identify virtual cards. If you are not working with virtual cards, you may ignore this flag.

When is this change happening?

The new field will be released on December 27th 2017.

Wednesday, January 31, 2018 - Webhooks

What is changing?

We are depreciating the sandbox URLs and replacing them with the new URLs.
This change will affect only Sandbox environment and not any other environment.
Below is the comparison between old URLs and new URLs

OLD URLs NEW URLs
External APIs https://corebeta.pexcard.com/api/v4/ping https://sandbox-coreapi.pexcard.com/v4/ping
Admin web site https://corebeta.pexcard.com/apps/admin.html https://sandbox-admin.pexcard.com/admin.html
Card holder web site https://corebeta.pexcard.com/apps/cardholder.html https://sandbox-ch.pexcard.com/cardholder.html

We are terminating the POST/Card/Create endpoint.
Currently PEX offers two separate end points to create cards POST Card/Create and POST/Card/CreateAsync.
POST/Card/CreateAsync will continue to exist for creating cards.

Finally, you should no longer be relying on maintaining an IP whitelist for webhook origination verification. PEX includes a security header in all webhooks that should be used to verify the origin of any webhook calls.


How does it affect you?

Plan on consuming new Sandbox URLs.

Please plan to use POST/Card/CreateAsync going forward if you are using POST/Card/Create.
POST/Card/Create creates a card order with a single card per request and POST/Card/CreateAsync can be used for creating a card order with single or multiple cards per request. Both the end point have same request structure.

Plan on checking webhook header to make sure the webhook notification is sent by PEX.

When this change is happening?

We will release this change on January 31, 2018.

Saturday, March 31, 2018 - API

What is changing?

V1 webhooks are being depreciated. You will no longer receive any calls on your V1 endpoints. If you wish to receive webhook notifications, please contact API support to receive V2 notifications.

How does it affect you?

If you wish to continue using Webhook notifications, please plan on switching to the V2 version.

When this change is happening?

We will release this change on March 31, 2018.

©2007-2024 Prepaid Expense Card Solutions, Inc., All Rights Reserved
The PEX Visa® Prepaid Card and the PEX Disburse Visa Prepaid Card are issued by Fifth Third Bank, N.A., Member FDIC, or The Bancorp Bank, N.A., Member FDIC, pursuant to a license from Visa U.S.A Inc and may be used everywhere Visa Prepaid cards are accepted. The PEX Prepaid Mastercard® is issued by The Bancorp Bank pursuant to license by Mastercard International Incorporated and may be used everywhere Debit Mastercard is accepted. Mastercard is a registered trademark, and the circles design is a trademark of Mastercard International Incorporated. Please see the back of your card for its issuing bank.
Android is a trademark of Google Inc. iPhone is a trademark of Apple Inc., registered in the U.S. and other countries. App Store is a service mark of Apple Inc. All trademarks and brand names belong to their respective owners. Use of these trademarks and brand names do not represent endorsement by or association with this card program.